Skip to content

Implement configuration API specification#10

Draft
MrtnvM wants to merge 1 commit intomainfrom
cursor/implement-configuration-api-specification-2ec1
Draft

Implement configuration API specification#10
MrtnvM wants to merge 1 commit intomainfrom
cursor/implement-configuration-api-specification-2ec1

Conversation

@MrtnvM
Copy link
Owner

@MrtnvM MrtnvM commented Sep 24, 2025

Implement the Configuration API endpoints and core logic to serve backend-driven UI schemas, including versioning, caching, and experiment resolution, as per the configuration-api.spec.md specification.

This PR introduces the GET /api/v1/config and GET /api/v1/config/default endpoints, along with the necessary domain entities, application services, use cases, and DTOs. It also includes mock experiment resolution, HTTP caching (ETag, Last-Modified), and a fallback mechanism to default schemas. A CONFIGURATION_API_README.md has been added for comprehensive documentation.


Open in Cursor Open in Web

This commit introduces the Configuration API, including endpoints for fetching configurations, handling version compatibility, and mock experiment resolution. It also establishes the necessary domain, application, and infrastructure layers for this functionality.

Co-authored-by: max.mrtnv <max.mrtnv@gmail.com>
@cursor
Copy link

cursor bot commented Sep 24, 2025

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants