Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Per https://twitter.com/jsonapi/status/909832481205039105:
How would you like us to write our name? (Please consider this to be case-insensitive)
17% JSONAPI
29% JSON API
47% JSON:API
7% other
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 3007431-9.patch | 141.54 KB | wim leers |
| #5 | Screen Shot 2018-10-17 at 09.14.56.png | 56.68 KB | gabesullice |
| #5 | Screen Shot 2018-10-17 at 09.14.44.png | 28.12 KB | gabesullice |
| #5 | Screen Shot 2018-10-17 at 09.14.34.png | 20.71 KB | gabesullice |
| #5 | Screen Shot 2018-10-17 at 09.14.29.png | 12.44 KB | gabesullice |
Comments
Comment #2
wim leersThis updates all user-facing strings.
Before updating all comments too, we should first confirm that this is something we want to do.
Comment #3
e0ipsoI like JSON API the most. Just because it's the status quo.
Also updating external documents, articles, 3rd party software, video tutorials,... is very hard. Leaving it as is is the minimum effort.
I think Gabe also said years ago that his preference was JSON API. Let's see if he still has that opinion nowadays.
Comment #4
wim leersWFM, but if pretty much everybody/everything else, including the spec writes
JSON:API, that's weird too.There's no good choice here.
It's a bad spec name :)
Comment #5
gabesulliceYep, you remembered correctly!
And I do still feel like "JSON API" is correct.
FWIW, less than 50% of respondents said they prefer "JSON:API". IOW, 53% do not use "JSON:API".
The spec does not write "JSON:API". The only place it appears that way is in the logo, and that's because it's emulating JSON:
{json:api}Everywhere that the name is actually written, it's "JSON API". See the many attached screenshots :)
Comment #6
gabesulliceCount me contradicted: https://github.com/json-api/json-api/pull/1318
Given this official endorsement, I've changed my mind. @e0ipso, thoughts?
Comment #7
e0ipsoYeah, that changes things. Let's do it.
Comment #8
gabesulliceI think this change could happen before 2.0 is stable. In fact, that might be preferable.
I'll leave this as RTBC and let another maintainer commit it, if they agree.
Comment #9
wim leersIndeed.
But this can't be RTBC yet, see #2:
Comment #10
wim leersChanged the project name & page!
Comment #11
wim leersIt's no longer a question; it's happening.
Comment #12
wim leersI'd commit this, but this will A) require every patch to be rebased, B) is trivial yet huge, and therefore I think we should get explicit +1s from all maintainers.
Comment #13
gabesulliceI'm very confused. See #7 and #8. Is that not explicit +1?Ohh, I get it. I didn't see your new patch. That's what needs explicit +1. I was thinking we would just commit the public facing changes.
I'm fine with the large patch. +1 lol.
Comment #14
gabesulliceAssigning to @e0ipso for commit or +1.
Comment #16
e0ipsoFixed!
Comment #17
wim leers🎉
Comment #18
wim leersLet the rebase party begin 🎉 🙈 😄
(Fortunately, we're pretty much at an all-time low in number of patches being reviewed, since we're pretty much bug-free now 🤘)
Comment #19
gabesullice🎉
Comment #20
wim leersWe missed a few: #3015343: Follow-up for #3007274: s/JSON API/JSON:API/ in *.module files.
Comment #22
wim leersFYI: I also just updated all documentation at https://www.drupal.org/docs/8/modules/jsonapi and its subpages.
Comment #23
gabesulliceOh, I know. RIP my inbox.
Comment #24
wim leers😂