What happened?
Right now, an entity supports this configuration:
"rest": {
"enabled": true,
"path": "/customers"
},But it does not support a subfolder like this:
"rest": {
"enabled": true,
"path": "/jerry/customers"
},
Note the jerry folder.
The value of this approach would be to let customers design the structure of their endpoints into folders. In simple examples with 1 or 10 endpoints, this may not seem apparent. But introduce 20 or 100 or even 1,000 endpoints and grouping them like this makes them far more sensible.
Note: Kamil Kliczbor (@kliszaq) #1638 (comment)
Version
Future
What database are you using?
Azure SQL
What hosting model are you using?
Local (including CLI)
Which API approach are you accessing DAB through?
REST
Relevant log output
No response
Code of Conduct
What happened?
Right now, an entity supports this configuration:
But it does not support a subfolder like this:
The value of this approach would be to let customers design the structure of their endpoints into folders. In simple examples with 1 or 10 endpoints, this may not seem apparent. But introduce 20 or 100 or even 1,000 endpoints and grouping them like this makes them far more sensible.
Note: Kamil Kliczbor (@kliszaq) #1638 (comment)
Version
Future
What database are you using?
Azure SQL
What hosting model are you using?
Local (including CLI)
Which API approach are you accessing DAB through?
REST
Relevant log output
No response
Code of Conduct