-
Notifications
You must be signed in to change notification settings - Fork 29
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
Issue with expansion test t0004 #310
Comments
The result of 13.4.11.2 is, indeed, a map of the form It is only at the outer level that the API algorithm comes in to place to make sure that the value of there outermost map gets wrapped in an array. Values of properties always get represented as arrays due to 13.14.2. |
I don't see how 13.14.2 helps here. I believe in this case, the value it will be appending to a list is:
The list being appended to is
But the test is expecting this:
I think the list introduced in 13.14.2 is operating at the wrong level. It needs to happen somewhere between the value being set to |
It looks like 13.4.11.2 should add the words "ensuring that the result is an array." as is done in 13.4.6. |
I actually had a FIXME in my code that this needed to be added! Let me know if that does it. |
@gkellogg the proposed change too 13.4.11.2 is in fact what I had come up with in attempting to move past this issue, and the wording now matches 13.4.6.2. Looks good. |
Expansion test t0004 seems to expect the value from the recursive expansion call in 13.4.11.2 to be an array, but it's coming back (from Value Expansion) as a map. This seems related to #299 which would have ensured that the value coming back form the recursive call was an array.
If t0004 represents the expected behavior, does 13.4.11.2 need to duplicate some of the post-processing that #299 moved into the JsonLdProcessor API?
The text was updated successfully, but these errors were encountered: