Azure / Azure/data-api-builder
[Enh]: For auto-config entities support `views`
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 372
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 9
Description
What?
Support views as well as tables in autoentities.
[!NOTE]
This feature supports only read-only views.
Why?
Because many customers, especial with MCP, prefer views.
How?
This is tricky because views do not have keys, which we currently require. The only viable solution without adding significant complexity is to include views as read-only entities. However, we currently don't have this concept. But it is coming!
- #2791
This prerequisite task introduces read-only views and enables this feature.
Configuration
{
"autoentities": {
"default": {
"source-type": [ "view" ] // default: [ table ]
}
}
}
An autoentity can include more than one type.
Command line
dab auto-config <name> --source-type "table,view"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the autoentities configuration and the dab auto-config command described in the issue, then read prerequisite issue #2791 about read-only views. The work is complete when autoentities accepts source-type values including view and the command supports --source-type "table,view" for read-only views.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100