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

Progressively adapt old API routes to fastAPI #10889

Open
26 of 55 tasks
mvdbeek opened this issue Dec 10, 2020 · 2 comments
Open
26 of 55 tasks

Progressively adapt old API routes to fastAPI #10889

mvdbeek opened this issue Dec 10, 2020 · 2 comments
Labels
area/API help wanted also "hacktoberfest", beginner friendly set of issues planning

Comments

@mvdbeek
Copy link
Member

mvdbeek commented Dec 10, 2020

This is not high-priority (the old routes aren't broken and will continue to work), but it would be great if we can get as many people as possible to get their hands on this task.

An example PR to add fastAPI routes is here: #11056
We are aiming at following the fastAPI documentation closely.
We will try to keep the routes as simple as possible, pushing complex logic into managers as much as possible.
Schema models may either live next to the manager code, or in lib/galaxy/schema/ for models that are used in
different parts of the app. Schema models for database models should always go to lib/galaxy/schema.

If you have any questions, please ask here or on gitter

List of files in lib/galaxy/webapps/galaxy/api/ :
(To prevent duplication of effort, please put down your GitHub username next to the controller you're working on)

@bgruening

This comment has been minimized.

@mvdbeek

This comment has been minimized.

@mvdbeek mvdbeek added help wanted also "hacktoberfest", beginner friendly set of issues planning labels Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/API help wanted also "hacktoberfest", beginner friendly set of issues planning
Projects
None yet
Development

No branches or pull requests

2 participants