Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): bump @nextcloud/l10n from 2.2.0 to v3 (main) #10307

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 30, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nextcloud/l10n ^2.2.0 -> ^3.1.0 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

nextcloud-libraries/nextcloud-l10n (@​nextcloud/l10n)

v3.1.0

Compare Source

Added
  • Allow setting escape option per parameter replacing.
    For more security this should be used instead of disabling paramter escaping,
    see pull request #​756
    // Example
    t(
    	'my-app',
    	'{a}{userInput}{a_end}',
    	{
    		a: {
    			value: '<a>',
    			escape: false,
    		},
    		userInput: somePossiblyInsecureValue, // This will be escaped
    		a_end: {
    			value: '</a>',
    			escape: false,
    		}
    	},
    )

v3.0.1

Compare Source

Fixed
  • Ensure that built type definitions are bundled with the release and located in the correct directory

v3.0.0

Compare Source

Full Changelog

Breaking changes

Instead of also sanitizing the replacing variables, now only the result is sanitized, see pull request #​648.

This will improve the performance if multiple placeholders are used and it allows this,
while the string is still sanitized:

t(
	'See {linkstart}documentation{linkend}',
	{
		linkstart: '<a ...>',
		linkend: '</a>',
	},
	// No number
	undefined,
	{
		// Do not escape the result as we want the HTML anchor element
		escape: false,
	}
)
Added
  • feat: export aliases t and n for translate and translatePlural
Fixed
  • fix!: Only sanitize the result string when replacing variables
Changed
  • Update NPM to latest LTS v10
  • Migrate to vite for transpiling and vitest for testing
  • chore: Added more tests for special cases on plural forms
  • chore(deps): Bump tough-cookie to 4.1.3
  • chore(deps): Bump postcss to 8.4.31
  • chore(deps): Bump @​nextcloud/typings to 1.8.0
  • chore(deps): Bump dompurify to 3.1.1
  • chore(deps): Bump @​nextcloud/router to 3.0.1

Configuration

📅 Schedule: Branch creation - "before 5am on wednesday" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot requested a review from GretaD as a code owner October 30, 2024 03:07
@renovate renovate bot requested a review from kesselb as a code owner October 30, 2024 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants