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

Modularise schema #36

Closed
fnoop opened this issue Apr 17, 2018 · 3 comments
Closed

Modularise schema #36

fnoop opened this issue Apr 17, 2018 · 3 comments

Comments

@fnoop
Copy link
Member

fnoop commented Apr 17, 2018

Api and Schema is all currently in a couple of big files which makes it difficult to add new modules/features. Would be much easier if the logic for each area was broken out into separate python modules.

@SamuelDudley
Copy link
Member

This is really important and is high on my list of things to do. Currently I think the schema and the mavros callback functionality should live together in a discreet module.

@SamuelDudley
Copy link
Member

Generate a structure so that tornado IO loop callbacks, mavros callbacks and schema can live in one "module". For now each module will be loaded at runtime, with the plan to add module loading controls at a later date.

@SamuelDudley
Copy link
Member

SamuelDudley commented Jan 6, 2019

Closing as the new api code has allowed this to move forward. See #55 for further work.

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

No branches or pull requests

2 participants