CHANGELOG: record the loader's parser-owned src resolution - #1676
Merged
Merged
Conversation
Filed under `### Changed` rather than left out. The refactor preserves behaviour and `setParser(type, fn)` is unchanged, so by the usual rule it is commit-history material — but the capability it introduces is real: a type whose `src` is not a bare path can now own its own resolution, which is something a reader can act on, and the entry says so in those terms rather than describing the internals. Credits @ICOM725, who did the original work. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NGvtaUNATVCVxD2qcbiY4t
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.
Adds the 20.7.0 entry for #1653 / #1648.
Filed under
### Changed. The refactor preserves behaviour andsetParser(type, fn)is unchanged, so under the usual rule it would be commit-history material — but the capability is real and actionable: a type whosesrcis not a bare path can own its own resolution. The entry is written in those terms rather than describing the internals.Credits @ICOM725 for the original work.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NGvtaUNATVCVxD2qcbiY4t