Skip to content

expansion: add test for default language - #702

Closed
daenney wants to merge 1 commit into
w3c:fix/fork-pr-report-generationfrom
daenney:default-lang-value-typemapping
Closed

daenney wants to merge 1 commit into
w3c:fix/fork-pr-report-generationfrom
daenney:default-lang-value-typemapping

Conversation

@daenney

@daenney daenney commented Aug 3, 2026

Copy link
Copy Markdown

This adds a test to check that when the context has a default language and we're expanding a string value that has a type mapping, the default language is not added.

It ensures Step 5 in Value Expansion is only performed for string values in the absence of a type mapping.

Fixes: #700

@daenney

daenney commented Aug 3, 2026

Copy link
Copy Markdown
Author

I opted to name this one t0133 to avoid clashing with #686.

@daenney

daenney commented Aug 3, 2026

Copy link
Copy Markdown
Author

@anatoly-scherbakov It seems I need to apply to join the WG as an invited expert to be able to join and then sign what the IPR commitments thing is?

@w3cbot

w3cbot commented Aug 4, 2026

Copy link
Copy Markdown

anatoly-scherbakov marked as non substantive for IPR from ash-nazg.

@anatoly-scherbakov
anatoly-scherbakov changed the base branch from main to fix/fork-pr-report-generation August 4, 2026 17:06
This adds a test to check that when the context has a default language
and we're expanding a string value that has a type mapping, the default
language is not added.

It ensures Step 5 in Value Expansion is only performed for string values
in the absence of a type mapping.

Fixes: w3c#700
@anatoly-scherbakov
anatoly-scherbakov force-pushed the default-lang-value-typemapping branch from ed895ed to 5f57f2c Compare August 4, 2026 17:08
@anatoly-scherbakov

Copy link
Copy Markdown
Contributor

@daenney thanks for contributing this!

  • I have marked this PR as non-substantive to prevent the ipr bot from complaining,
  • There was another CI failure, I fixed it in another PR,
  • and then I rebased this PR on top of mine to test that CI is now 🟢, sorry for messing with your PR and hope that this does not cause inconvenience!

Now we'll need both of these PRs approved by someone with write access, I added people as reviewers to both.

@daenney

daenney commented Aug 5, 2026

Copy link
Copy Markdown
Author

No worries at all, thanks for doing all this!

@anatoly-scherbakov
anatoly-scherbakov deleted the branch w3c:fix/fork-pr-report-generation August 12, 2026 16:13
@anatoly-scherbakov

Copy link
Copy Markdown
Contributor

@daenney I am afraid we accidentally closed this :/ PR stacks over forks do not behave as I intended. Would you be open to raise it again? I am sorry!

@TallTed TallTed left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@anatoly-scherbakov

Copy link
Copy Markdown
Contributor

Or otherwise I can look into recreating it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

expansion: string @value must not get @language/@direction if type mapping exists

5 participants