Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow REST API exclude M2M fields #6556

Open
lampwins opened this issue Nov 19, 2024 · 0 comments
Open

Allow REST API exclude M2M fields #6556

lampwins opened this issue Nov 19, 2024 · 0 comments
Assignees
Labels
emergent Unplanned work that is brought into a sprint after it's started. ms type: enhancement Enhancement to existing functionality of the application

Comments

@lampwins
Copy link
Member

To support cases where many to many fields degrade performance of API responses (even in depth 0 cases), introduce support to ignore/exclude M2M fields in the API response.

So an API consumer can specify ?exclude_m2m=true and not get any M2M fields at all in the response. This is particularly needed in problem areas like VRF where there are several M2M relationships and frequent opportunity for data scale. The API select2 widget will generally benefit from this across the board.

@lampwins lampwins added type: enhancement Enhancement to existing functionality of the application ms labels Nov 19, 2024
@glennmatthews glennmatthews self-assigned this Nov 26, 2024
@glennmatthews glennmatthews added the emergent Unplanned work that is brought into a sprint after it's started. label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emergent Unplanned work that is brought into a sprint after it's started. ms type: enhancement Enhancement to existing functionality of the application
Projects
None yet
Development

No branches or pull requests

2 participants