-
-
Notifications
You must be signed in to change notification settings - Fork 203
improv/execQuery legibility #1105
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
base: 21.x
Are you sure you want to change the base?
Conversation
Hey @will-apresenta! ππ» May you add some tests to your PR? |
Hi @RomainLanz, I've didn't created any test because it don't change the functionality itself, but i can create some if needed |
Hi, @RomainLanz, i didn't found any test to execQuery, but all the existing tests run well |
Correct, but it will avoid us to break those contract. At least, you could add a test that mimic your usecase (use a custom query builder). |
Hi @RomainLanz, I'm struggling how to always call execQuery. In short, i'm trying to create a cache on model level, it means, i will be able to configure cache on each model, including disable it, so i will need model class to be accessible where it created query and executes. Before making the PR, i've tested it on my adonisjs application and overriding execQuery with macro worked, but i've forgoten to test saving relations, so now creating tests to lucid i've realized that My test:
|
π Linked issue
β Type of change
π Description
Improves legibility to execQuery and exports QueryRunner to make it easier to extend
Resolves #1102
π Checklist