Skip to content

Use JSON:API instead of JSON API #1318

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

Merged
merged 3 commits into from
Oct 31, 2018
Merged

Conversation

kocsismate
Copy link
Contributor

As mentioned in #1317, I changed "JSON API" to "JSON:API" everywhere I could. Do you see any part where we should just stay with "JSON API"? E.g. I was unsure if I can change it in the description of the implementations (but I didn't touch their names).

Copy link
Member

@ethanresnick ethanresnick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but I'll let @dgeb weigh in too.

@dgeb dgeb merged commit ff35bb2 into json-api:gh-pages Oct 31, 2018
@dgeb
Copy link
Member

dgeb commented Oct 31, 2018

LGTM as well. Thanks much @kocsismate!

@wimleers
Copy link
Contributor

wimleers commented Nov 8, 2018

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

Successfully merging this pull request may close these issues.

4 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy