-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Remove web framework dependency from tools #17058
Remove web framework dependency from tools #17058
Conversation
3316d84
to
d8dfeac
Compare
If you are not planning to create a new package for cd packages/app/galaxy/
ln -s ../../../lib/galaxy/short_term_storage/ to fix the package tests? |
I was actually planning to create a new package but with your help (just wrote to you on Matrix at the same time 😆) but I will add the symlink meanwhile 👍 |
5b455a0
to
518e6b8
Compare
71e1eba
to
192e890
Compare
I think I managed to remove all I could spot so opening for review. Is there some known Pythonic sorcery to check there are no more dependencies left? |
Once/if we split out a tools&workflow package from app, package testing should find out... |
- Use `util.unicodify` in copy_view.mako for consistency with other usages of unicodify in the file. - Move `to_unicode` to the only place it's used under tool/search/__init__.py
The ShortTermStorageManager is a manager and makes sense to have it live under galaxy.managers instead of galaxy.web. It will also help reduce the dependency of the manager modules on web related stuff.
- And rename it to `api_error_to_dict` since it creates dictionary with and not a message string as the previous name might suggest.
Co-authored-by: Nicola Soranzo <[email protected]>
Co-authored-by: Nicola Soranzo <[email protected]>
The ShortTermStorageManager and related classes should live in their own package eventually and not within galaxy.web nor galaxy.managers as the short term storage microservices it's fairly independent and has way less dependencies than those other packages.
Co-authored-by: Nicola Soranzo <[email protected]>
Temporarily include it in app until the STS goes into its own package.
Temporarily until we create its own package.
We need to use url_builder from the request context to be able to generate valid URLs. Hopefully url_for_not_available will help identify any other possible use of url_for that does not fall back into url_builder.
Replace calls to web.url_for with compatible url_builder.
Replace calls to web.url_for with compatible url_builder. Since there is no real API route for those (they live in client controllers) we need to pass the path prefix as name...
Both links `{host}/activate` and `{host}/user/activate` work but the latter seems more explicit about what are we trying to activate. Co-authored-by: Nicola Soranzo <[email protected]>
Taking the server_starttime from app instead.
Mostly for consistency with other similar functions in the module. Co-authored-by: Nicola Soranzo <[email protected]>
This should fix URL generation for collections by using the URL builder instead of the legacy url_for.
3671279
to
4eb22fe
Compare
This package is used by pulsar with still supports Python 3.7
8701ff7
to
1ef8e6a
Compare
Part of #17046
This tries to remove several imports of
galaxy.web
fromgalaxy.tools
andgalaxy.managers
.Most changes involve handling URL generation without directly importing
galaxy.web.url_for
.How to test the changes?
License