-
Notifications
You must be signed in to change notification settings - Fork 154
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
Fixed returned @context issues when the context is a remote context #296
Conversation
066c3db
to
0148848
Compare
0148848
to
47a595a
Compare
06f9ccb
to
b784f3f
Compare
As far as I have seen in the spec and in the tests done in the playground, the passed context is the one that has to be provided as a result, not the resolved one or anything else. It still passes the tests from the W3C suite, so I assume there is no further problem with it. |
99b35ab
to
e87a1f3
Compare
e87a1f3
to
99f8ae0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First of all: thx a lot for your contribution. This fixes a bunch of issues which is really great!
Note that I opened a PR against your branch, just some minor cleanup.
core/src/main/java/com/github/jsonldjava/core/JsonLdProcessor.java
Outdated
Show resolved
Hide resolved
I've added the changes from your PR in my latest commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs some clarification about the removal of the Context.serialize
method.
83a6eb1
to
4894387
Compare
Looks good, thanks. Will release today. |
Fixes #295
Fixes #184
Fixes #297
Fixes #298