Skip to content

refs vs references #41

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.

Sign up for GitHub

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

Jump to bottom
Open
aaronpk opened this issue Jun 25, 2018 · 5 comments
Open

refs vs references #41

aaronpk opened this issue Jun 25, 2018 · 5 comments

Comments

@aaronpk
Copy link
Member

aaronpk commented Jun 25, 2018

Not sure how this happened, but XRay, Monocle, Together and others are using the property called refs instead of references.
@swentel
Copy link

swentel commented Jan 2, 2019 •
edited
Loading

isn't that because xray puts in the 'refs' key ? - stupid comment, never mind

@dshanske
Copy link
Member

I just changed over to refs for my Parse This due multiple adoptions above, which is used by Yarns as a dependency.

@swentel
Copy link

swentel commented Jan 29, 2020

fwiw, Drupal uses xray, so it stores refs.
Indigenous looks for the refs property at the moment.

@jalcine
Copy link

jalcine commented Jul 4, 2020

I don’t have refs used in the IndieWeb Elixir yet but I’m in favor of shorter keys!

(Originally published at: https://v2.jacky.wtf/post/6fb712f9-9e03-4b71-ac3d-eb2d4d6fa382)

@jalcine
Copy link

jalcine commented Mar 20, 2023

Bumping this, I've opted to stick to references to remain spec-compliant in the Rust Microformats parser (and can update the Elixir to align).

(Originally published at: https://jacky.wtf/2023/3/W5j7)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@aaronpk @swentel @jalcine @dshanske