✅ Development Roadmap (as of June 2024)

[yorek]

Here's the planned roadmap. We'll update this post as soon as we move forward with the development. Subject to change.

1.1 (May 2024)

• ✅ Complete multiple create support for GQL (A&S)
• ✅ Upgrade to .NET 8 (SL)

1.2 (July 2024)

• Stabilization release.
• [Pre-Release] v1.2.9-rc

1.3 (September 2024)

• Hot Reload of the Configuration file (AB) #
  • Include runtime support.
  • Include entity support (tentative).
• Introduce dab configure to the CLI (AK) [Enhancement]: Introduce dab configure #2251
• Expand Cache implementation (SL) ⭐ [Enhancement]: "Complete" Cache Features #2253
  • HTTP request header no-cache, no-store.
  • Add CLI implementation for cache in runtime and entity.
  • Default runtime cache enabled to true when enabled an entity (in CLI)
  • Add support for stored-procedure entities.

1.4 (preliminary)

• Entity & field metadata
• Role-specific OpenAPI
• Output parameters
• Custom error messages
• Define relationships between views

Additional backlog

• Introduce REST keyword OData & LINQ synonyms [Enhancement]: $first & $after keywords in REST & GQL #2246
  • We have $after & $skip
  • We want $first & $take
• Substring operations in item-level security
• Custom logic at pre/post query
• Linked table columns in GraphQL
• Support JSON data type in mssql
• Configuration UI / editor
• Create dab-config.json from dacpac
• Enable caching with Session Context
• Additional native authentication providers
• Update authentication provider simulator to support access token claims mocking
• Native integration with Azure App Services
• Subscriptions for GraphQL endpoints
• REST support for new $count aggregate-value keyword
• REST support for new $value scalar-value keyword
• Introcuce OData endpoint

Archive

0.7 (May 2023)

• ✅ Support for OpenAPI v3
• ✅ Executing GraphQL and REST Mutations in a transaction
• ✅ Add support for Cosmos field level authorization
• ✅ Database policy support for PUT/PATCH operations
• ✅ Adding Merge config capabilities to CLI

0.8 (July 2023)

• ✅ Add support for .env file

0.9 (September 2023)

• ✅ Add support for Application Insights
• ✅ Mutations on table with triggers
• ✅ Support for ignoring extraneous fields in rest request body
• ✅ Adding support for positive boolean options in CLI
• ✅ Structured logging compatibility
• ✅ Adding Application Name for mssql connections
• ✅ Support time data type in mssql

0.10 (November 2023)

• ✅ Caching support for REST & GQL endpoints (SL)
• ✅ Partial nested mutation support for GQL (A&S)
• ✅ Improved support for time data type in mssql (AA)
• ✅ Support validate in the CLI (AK)

0.11 (January 2024)

• ✅ Support multi-data sources & config files (RK)
• ✅ Support for Synapse (RK)

[tsitsimis]

Hi and thank you for the great work!

I understand from the feature requests that Synapse is not supported. Does this mean I can't use the connection string of a Dedicated SQL Pool as if it was a standard SQL Server to configure Data API Builder?

Cheers!

[Aniruddh25]

@tsitsimis, you are right. At the moment, Synapse is not supported.

You could use the connection string to connect to Dedicated SQL Pool but querying the APIs would error out. This is because the APIs need JSON as a response, and we rely on FOR JSON PATH to get a JSON response as per https://learn.microsoft.com/en-us/sql/relational-databases/json/format-query-results-as-json-with-for-json-sql-server?view=azuresqldb-current. This method to get JSON response is not supported by Dedicated SQL Pool yet - so we need to enhance DAB to handle such scenarios on the roadmap.

[zebleck]

Would be great if policies allowed for checking many-to-many relationships. For example, we want to only allow reading an entity if its many-to-many relationship with the User entity contains a user with @claims.userId.