Repository navigation
feat: establish JavaScript values and packaging - #16
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Establish the case-sensitive
JavaScriptpackage and its published companion dependency ranges. Add shared undefined, truthiness, binary64 conversion, equality and callback operations so later objects use one consistent semantic foundation. Remove the scaffold command and add installed-wheel CI on Linux, macOS and Windows with Python 3.14.Validation: seven value tests pass from source and from an isolated built wheel with the candidate Fetch 0.2.0 wheel and published JSON 0.1.0. The sdist and wheel build successfully. CI will resolve both companions from PyPI once FET-01 is published.
Closes #2. Depends on outside-labs/JavaScript-Fetch-API#2. Project: https://github.com/orgs/outside-labs/projects/11