Rules for dropping free-floating values in Expansion Algorithm
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 106
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
The wording of step 19.1 is:
If result is a map which is empty, or contains only the entries
@valueor@list, set result to null.
That only indicates that only an untyped (string) literal or a list should be suppressed during expansion of a null or @graph active property. However the test suite indicates that this should also happen for language-tagged strings and for typed literals (which completely makes sense!).
Does that test at step 19.1 need to be broadened to include data-typed or language-tagged literals or have I missed something in the preceding part of the algorithm that would have caused the free-floating value to be dropped before step 19.1?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading step 19.1 and the preceding expansion-algorithm steps, then inspect the referenced test suite for how free-floating language-tagged and typed literals are handled. Done means resolving whether the algorithm wording or its test coverage must change, with the specification and tests agreeing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100