-
Notifications
You must be signed in to change notification settings - Fork 0
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 feature flags easier to use and fix database errors #140
Conversation
specifying the type of feature flag router as a separate module.
023d8c8
to
ffd1829
Compare
The `cast` for the FeatureFlagRouters is necessary for Injector to correctly resolve and inject instances of the type. The actual type is `Self | FeatureFlagRouter[...]`, but the usages of the injected type do not rely on `Self`, which messes up how Injector resolves dependencies.
Ligare needs a way to understand the base SQLAlchemy classes involved in querying a database. This is for a few reasons: - schema translation for systems that don't support schemas - supporting schemas in general - not overwritting `ScopedSession` registration when multiple `ScopedSession` instances are registered with Injector
This protects the class against modifications from instantiations during an application runtime. It also resolves static type errors from private member usages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool! Code looks good. A lot of familiar patterns for db sessions from CAP. If you have a free moment, could you add a quick usage example with the improvements?
Yes, I will add some docstrings and some examples to the "cookbook" idea. |
Cookbook is perfect! |
This PR:
feature_flag
decoratorLigare.web
application contexts