Skip to content

CLARIN-DSpace v9: fix double encoding of CLARIN license names containing '+' - #1638

Open
milanmajchrak wants to merge 1 commit into
dtq-dev-9-basefrom
9-base/fe-clarin-license-name-encoding
Open

milanmajchrak wants to merge 1 commit into
dtq-dev-9-basefrom
9-base/fe-clarin-license-name-encoding

Conversation

@milanmajchrak

@milanmajchrak milanmajchrak commented Oct 20, 2026 •

Copy link
Copy Markdown
Collaborator

References

Port of dtq-dev PR 1596 (commit c3c44fc).

Description

findClarinLicenseByName() encoded a license name with + once more than RequestParam already does, so the byName lookup asked for GNU%2520GPL%25202.0%252B and found nothing. The extra encodeURIComponent is gone.

Instructions for Reviewers

  • section-license.component.ts: the if (licenseName.includes('+')) block is removed, RequestParam encodes the value itself since the 7.6.5 upgrade
  • spec: the byName query is name=GNU%20GPL%202.0%2B for GNU GPL 2.0+ and name=Licence%20A%20%26%20B for Licence A & B
  • written for the 9.x spec, the two new tests sit next to the create test
  • section-license.component.spec.ts passes locally (17 tests), eslint clean

Checklist

  • My PR is created against the branch it ports to
  • My PR is small in size
  • My PR follows the code conventions and passes ESLint
  • My PR passes all specs and includes new or updated specs
  • My PR includes details on how to test it
  • No new dependencies, no new configuration

🤖 Generated with Claude Code

…ing '+'

Port of dtq-dev PR 1596 (commit c3c44fc) to the v9 base, written for the 9.x spec.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant