What is it?

• The ability to customize REST paths with sub-directories, such as /api/sub-directory/books.

This improvement addresses potential conflicts that arise when multiple data sources contain entities with the same desired REST path. For example, you might have an Item entity under both an Invoice and a ShoppingCart. With the current setup, you might end up with paths like /shopping-cart and /shopping-cart-item, when the desired paths would be /shopping-cart/item and /invoice/item. This issue becomes more pronounced as we introduce tenant support across multiple databases.

Questions

1. How many sub-folders, just one? Yes. Just one.
2. Are paths unique across config files? Yes, required.

Related issues to close

• REST: Add support for url template with implicit primary key field names #1085
• [Enhancement]: The rest endpoint is in the background odata. But it doesn't present an OData MetadataEndpoint #1566