Changes for page HTTP Resources
Last modified by Erik Bakker on 2024/08/23 10:51
From version 24.1
edited by Danniar Firdausy
on 2024/08/21 10:55
on 2024/08/21 10:55
Change comment:
There is no comment for this version
To version 23.1
edited by Danniar Firdausy
on 2024/08/21 10:31
on 2024/08/21 10:31
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -22,12 +22,12 @@ 22 22 When determining the correct resource path to expose to the outside world, start at what you want to make publicly available. 23 23 For example, when you want to make it possible for external parties to retrieve a collection of orders without any filter a valid resource path can be: 24 24 25 -* {{code language=text}}/orders{{/code}}25 +* /orders 26 26 27 27 If you have multiple resources that you want to make available that all have something to do with the order process you could add each of them to a 'group' to add an extra layer of information: 28 28 29 -* {{code language=text}}/order-management/orders{{/code}}30 -* {{code language=text}}/order-management/trips{{/code}}29 +* /order-management/orders 30 +* /order-management/trips 31 31 32 32 To determine the correct notation also take into account how the backend system that you want to expose via the API Gateway has determined their HTTP Resource (Paths). 33 33 If this adheres to the best practice simply use that. More on that specific relation in later microlearnings.