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

Encode URI fragments #1216

Merged
merged 1 commit into from
Feb 23, 2023
Merged

Encode URI fragments #1216

merged 1 commit into from
Feb 23, 2023

Conversation

tidoust
Copy link
Member

@tidoust tidoust commented Feb 22, 2023

IDs cannot simply be prefixed with # and used as fragments. They need to be encoded first. Via w3c/webref#889

IDs cannot simply be prefixed with `#` and used as fragments. They need to be
encoded first. Via w3c/webref#889
@tidoust tidoust merged commit 46c4e29 into main Feb 23, 2023
@tidoust tidoust deleted the encode-fragment branch February 23, 2023 08:27
tidoust added a commit that referenced this pull request Feb 24, 2023
Breaking change:
- Skip non-published specs when "--release" option is set (#1214)

The change is breaking in that a crawl on released versions of specs no longer
contains info about specs that do not have a released version. For example,
specs that only exist as living standards such as WHATWG specs are no longer
crawled when the `--release` option is set. The `--release` option is typically
used to run a crawl that completes a crawl on the nightly versions of specs.
Goal of the change is to avoid crawling specs that are already in the nightly
crawl.

Crawl results are unaltered otherwise. Tools that use Reffy should only need to
update their logic if they expect a `--release` crawl to also yield info about
non-released specs.

Feature patches:
- ECMAScript spec: Fix dfn scoping and abstract op extraction (#1217)
- Drop legacyValue extraction logic (#1218)
- Encode URI fragments (#1216)
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.

2 participants