-
-
Notifications
You must be signed in to change notification settings - Fork 53
next release - feature parity - high testing coverage #148
Conversation
Codecov ReportBase: 84.46% // Head: 37.60% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #148 +/- ##
===========================================
- Coverage 84.46% 37.60% -46.87%
===========================================
Files 14 25 +11
Lines 1056 2284 +1228
===========================================
- Hits 892 859 -33
- Misses 164 1425 +1261
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Co-authored-by: Sourcery AI <>
|
What are the parts that are not covered by tests? |
Sourcery Code Quality Report❌ Merging this PR will decrease code quality in the affected files by 20.57%.
Here are some functions in these files that still need a tune-up:
Legend and ExplanationThe emojis denote the absolute quality of the code:
The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request. Please see our documentation here for details on how these metrics are calculated. We are actively working on this report - lots more documentation and extra metrics to come! Help us improve this quality report! |
Co-authored-by: Sourcery AI <>
…lementation of gotrue-js The tests still need to be implemented.
Co-authored-by: Sourcery AI <>
…0/patch_conflicts_on_next
…_next chore: patch merge conflicts on next
|
Hey @leynier, Thanks for putting this together! 🚀 Going to go ahead and merge this one in first but feel free to sound off if you have strong opinions about it please lmk and I'll revert. Think this would be really helpful for the general for the general public even without the desired test coverage |
This pull request is to sync the current implementation (maintaining a Pythonic approach) with the gotrue-js implementation to get both libraries to have feature parity.
We also want to do as much testing as possible to get as high testing coverage as possible (the main difficulty with testing is in methods where mobile phone service is used).
Finally, if the objectives of this pull request are achieved, move the version to v1 and consider this library stable (as much as possible).