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

Make it easier to serve provider fields with validation #929

Open
ml-evs opened this issue Sep 1, 2021 · 0 comments
Open

Make it easier to serve provider fields with validation #929

ml-evs opened this issue Sep 1, 2021 · 0 comments
Labels
ergonomics Features that improve the usability of the package priority/medium Issue or PR with a consensus of medium priority

Comments

@ml-evs
Copy link
Member

ml-evs commented Sep 1, 2021

Following the discussion from #925, we should make it easier to extend our models and make sure they get used for validation in the API.

Currently, this requires changing the associated endpoint, entry collection and mapper code to get working (as many have done in our forked implementations). This should be something that is configurable, presumably via something like: "data_models": {"structures": MyStructureModel} in the config (which can then set the appropriate entry info schemas, mapper resource class, collection response class etc.).

@ml-evs ml-evs added priority/medium Issue or PR with a consensus of medium priority ergonomics Features that improve the usability of the package labels Sep 1, 2021
@ml-evs ml-evs changed the title Difficult to serve provider fields with validation Make it easier to serve provider fields with validation Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ergonomics Features that improve the usability of the package priority/medium Issue or PR with a consensus of medium priority
Projects
None yet
Development

No branches or pull requests

1 participant