We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
And instead I think we would now recommend to use a scoped context, no?
{ "@context": { ... "@language": "ja" }, "name": "花澄", "details": { "@context": { "@language": null }, "occupation": "Ninja" } }
Would become
{ "@context": { ... "details": { "@context": { "@language": null } }, "@language": "ja" }, "name": "花澄", "details": { "occupation": "Ninja" } }
This pattern should at least be demonstrated, even if 67 isn't changed
The text was updated successfully, but these errors were encountered:
I don't know if we've said that embedded contexts aren't best practices, but I see no harm in updating the example.
Sorry, something went wrong.
Use a scoped, rather than an embedded context for default language ex…
d528735
…ample. Fixes #250.
fa3e312
Successfully merging a pull request may close this issue.
And instead I think we would now recommend to use a scoped context, no?
Would become
This pattern should at least be demonstrated, even if 67 isn't changed
The text was updated successfully, but these errors were encountered: