books/The-API-Book
1
0
Fork 0
mirror of https://github.com/twirl/The-API-Book.git synced 2025-05-19 21:33:04 +02:00
Code Issues Releases Activity

style fix

Browse Source
This commit is contained in:
Sergey Konstantinov 2023-03-05 15:41:49 +02:00 committed by GitHub
parent 44b0b8ef3d
commit a30f75c284
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/en/clean-copy/03-Section II. The Backwards Compatibility/04.md
View File

@ -203,11 +203,11 @@ We should also note that providing a newly created entity identifier by the requ
``` ```
POST /v1/recipes/custom POST /v1/recipes/custom
{ {
// First part of the composite // The first part of the composite
// identifier, for example, // identifier, for example,
// the partner's own id // the partner's own id
"namespace": "my-coffee-company", "namespace": "my-coffee-company",
// Second part of the identifier // The second part of the identifier
"id_component": "lungo-customato" "id_component": "lungo-customato"
} }
→ →
@ -217,4 +217,4 @@ POST /v1/recipes/custom
} }
``` ```
Also note that this format allows us to maintain an important extensibility point: different partners might have totally isolated namespaces, or conversely share them. Furthermore, we might introduce special namespaces (like `common`, for example) to allow for publishing new recipes for everyone (and that, by the way, would allow us to organize our own backoffice to edit recipes). Also note that this format allows us to maintain an important extensibility point: different partners might have totally isolated namespaces or conversely share them. Furthermore, we might introduce special namespaces (like `common`, for example) to allow editing standard recipes (and thus organizing our own recipes backoffice).