-
Notifications
You must be signed in to change notification settings - Fork 8
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
Bug fixes in Examples (PR #5 for issue #94) #112
Bug fixes in Examples (PR #5 for issue #94) #112
Conversation
@gkellogg please check this out when you have a moment 🙂 |
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.
I suggested using relative links for yaml files. If there is a rendering issue, this might be addressed differently.
spec/index.html
Outdated
@@ -342,7 +342,7 @@ <h2>Introduction</h2> | |||
|
|||
<div class="ednote"> | |||
See YAML-LD description of this spec at | |||
<a href="https://github.com/json-ld/yaml-ld/blob/main/spec/spec.yaml"> | |||
<a href="https://github.com/json-ld/yaml-ld/blob/main/spec/data/spec.yaml" target="_blank"> |
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.
It's cleaner to keep these references as relative to the spec, so when they're published, they show up properly. That would make it <a href="data/spec.yaml">...</a>
.
Done so, — but it would seem it does not render. For instance: https://pr-preview.s3.amazonaws.com/json-ld/yaml-ld/pull/data/spec.yaml does not work. |
PR Preview doesn't have access to associated files, but you can see them via GitHack. This better reflects how the spec will render when merged. |
Why
YAML-LD samples have a few bugs.
What
This PR is fixing those.
Preview | Diff