You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
A clear and concise description of what you expected to happen.
I would expect the values inside the friends list to be considered as ids and prepended the defined @base but it's not the case, although I take the same source Json and put it inside Json Playground and it works.
Here is a screenshot of the differences from Json Playground (on the left, Titanium on the right). Here we can clearly see that type coercion is applied in the Json Playground:
Additional context
Add any other context about the problem here.
I am using the latest distributed version (1.4.0), the same problem is present in Apache Jena 4.10.
The text was updated successfully, but these errors were encountered:
hyprdia
changed the title
Type Coercion not working inside @container inside @container
Type Coercion not working in a @container inside another @container
Apr 5, 2024
Describe the bug
A clear and concise description of what the bug is.
Type coecion is not applied when a
@container
is defined inside another@container
. In the example below I define friends as a container:This container is present inside the top
users
container:To Reproduce
Steps to reproduce the behavior:
Here is a test that will reproduce the bug:
Expected behavior
A clear and concise description of what you expected to happen.
I would expect the values inside the
friends
list to be considered as ids and prepended the defined@base
but it's not the case, although I take the same source Json and put it inside Json Playground and it works.Here is a screenshot of the differences from Json Playground (on the left, Titanium on the right). Here we can clearly see that type coercion is applied in the Json Playground:
Additional context
Add any other context about the problem here.
I am using the latest distributed version (
1.4.0
), the same problem is present in Apache Jena 4.10.The text was updated successfully, but these errors were encountered: