-
Notifications
You must be signed in to change notification settings - Fork 3
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
299 sdx controller must have new endpoints according to specification 20 #318
299 sdx controller must have new endpoints according to specification 20 #318
Conversation
Pull Request Test Coverage Report for Build 10464630503Details
💛 - Coveralls |
there are a few "unused" classes in models: for v2 and other future implementation |
It probably might be better to not use the generated models at all? A better way might be to write the models using pydantic in datamodel, and use them in the handlers and tests. That way we will be using Swagger Studio (or other tools) only to design the OpenAPI spec. I wrote up an issue about this: atlanticwave-sdx/datamodel#144. From my quick testing, I think pydantic might work just fine for us. This might also solve atlanticwave-sdx/datamodel#92 in an elegant way. |
Right! I'll learn and do...Thx |
I am only weakly proposing this for now, to see if there is anything that I am missing because I have no experience with the current workflow (of generating code and updating it in sdx-controller and elsewhere). I will try writing some code with pydantic and see how well things work, and then propose changes more strongly if my assumptions about how things might work turn out to be true. :-) We have higher priority things to do for now anyway. So this might be after October or so. |
spec v2: