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

Describe that type-scoped contexts are only in affect on the node objects in which they're used #195

Merged
merged 2 commits into from
Jun 20, 2019

Conversation

gkellogg
Copy link
Member

@gkellogg gkellogg commented Jun 19, 2019

Add changes for type-scoped contexts.

Fixes #174.


Preview | Diff

…ects in which they're used. Add changes for type-scoped contexts.

Fixes #174.
@gkellogg gkellogg requested review from dlongley and pchampin June 19, 2019 18:44
Copy link
Contributor

@dlongley dlongley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good -- I suggested a potential additional sentence that might help clarify things to address @pchampin's concern.

…ed when a type-scoped context is in effect remain in effect in descendant node objects.
@gkellogg gkellogg merged commit 3fb9b47 into master Jun 20, 2019
@gkellogg gkellogg deleted the type-scoped-context-refinement branch June 20, 2019 20:34
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.

Unexpected @type scope behavior (term definitions persist throughout JSON tree)
3 participants