Skip to content

Conversation

gregsdennis
Copy link
Member

No description provided.

@gregsdennis gregsdennis changed the title resolves #1019 - added language to explicitly specify behavior when a vocab is known added language to explicitly specify behavior when a vocab is known Nov 19, 2020
Copy link
Member

@Relequestual Relequestual left a comment

Choose a reason for hiding this comment

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

Single change suggestion. Semantics! 🙄

Otherwise, this PR is good to go.
Thanks for your effort in making it happen =]

@gregsdennis
Copy link
Member Author

merge when ready

@karenetheridge
Copy link
Member

Is a footnote necessary, to indicate that the handling for the format vocabulary is special-cased?

@gregsdennis
Copy link
Member Author

gregsdennis commented Nov 20, 2020

@karenetheridge no. Please see #1023 / #1026 for changes to format, which remove the special-case treatment. This change is purely for vocabularies.

@gregsdennis gregsdennis dismissed Relequestual’s stale review November 20, 2020 20:16

applied suggested changes

@gregsdennis gregsdennis removed the request for review from handrews November 21, 2020 11:46
@Relequestual Relequestual merged commit e6bead3 into master Nov 22, 2020
@handrews handrews deleted the issue-1019-known-vocabs-are-always-processed branch October 17, 2022 05:59
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.

$vocabulary:{<vocab>:false} when a vocab is recognized is not defined

3 participants