Add context-aware string projection for metadata fields - #1
Merged
Merged
Conversation
andrew
force-pushed
the
document-string-projection
branch
from
October 1, 2026 08:13
bb32ece to
7130f95
Compare
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
1 participant
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.
Consumers that need text from CodeMeta fields currently have to handle aliases and JSON-LD containers themselves. Add
Document.Strings(term)to extract strings, object identifiers, or object names in source order, with context-aware key resolution and support for lists, sets, and value objects.For example,
license: {"id":"https://spdx.org/licenses/MIT"}yields the license URL, andkeywords: {"@set":["science","metadata"]}yields both keywords. The accessor preserves the original values available throughGetand has regression coverage for context changes and key precedence.