Skip to content
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

render_path is empty for resource, which is not page.rdf #85

Closed
white-gecko opened this issue Jul 19, 2017 · 4 comments
Closed

render_path is empty for resource, which is not page.rdf #85

white-gecko opened this issue Jul 19, 2017 · 4 comments
Assignees
Milestone

Comments

@white-gecko
Copy link
Member

white-gecko commented Jul 19, 2017

The property render_path of an RdfResource is empty, if it is not the page.rdf resource.

MWE:

graph:

<http://example.org/Resource> <http://example.org/rel> <http://example.org/RelatedResource> .
<http://example.org/RelatedResource> <http://example.org/rel> <http://example.org/RelatedResource> .

template:

{% assign rel = page.rdf | rdf_property: '<http://example.org/rel>' %}
{{ rel.render_path }}

actual:
nothing

expected:

http://example.org/RelatedResource
@white-gecko white-gecko added this to the 2.1.1 milestone Jul 19, 2017
@white-gecko
Copy link
Member Author

Please also add a test for this

@Simaris
Copy link
Collaborator

Simaris commented Jul 27, 2017

it is somewhat intended behaviour since resources that are not used as page resources are not rendered. render_path is also somewhat redundant since page_url and render_path are currently nearly the same.

@white-gecko
Copy link
Member Author

The difference between page_url and render_path is also depicted in #94 .

@white-gecko
Copy link
Member Author

Closed by #101

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

No branches or pull requests

2 participants