supabase-py
supabase-py copied to clipboard
Continuation of Pr/234: ran isort and black for tests
Apologies if I'm doing something wrong - this is my first open source contribution. I'm running two tests to help pass checks for PR/234. This is the PR in question: https://github.com/supabase-community/supabase-py/pull/234
Sourcery Code Quality Report
❌ Merging this PR will decrease code quality in the affected files by 1.70%.
Quality metrics | Before | After | Change |
---|---|---|---|
Complexity | 2.27 ⭐ | 2.61 ⭐ | 0.34 👎 |
Method Length | 34.00 ⭐ | 36.58 ⭐ | 2.58 👎 |
Working memory | 7.11 🙂 | 7.54 🙂 | 0.43 👎 |
Quality | 78.35% ⭐ | 76.65% ⭐ | -1.70% 👎 |
Other metrics | Before | After | Change |
---|---|---|---|
Lines | 182 | 194 | 12 |
Changed files | Quality Before | Quality After | Quality Change |
---|---|---|---|
supabase/client.py | 82.48% ⭐ | 82.09% ⭐ | -0.39% 👎 |
supabase/lib/client_options.py | 65.59% 🙂 | 61.24% 🙂 | -4.35% 👎 |
Here are some functions in these files that still need a tune-up:
File | Function | Complexity | Length | Working Memory | Quality | Recommendation |
---|---|---|---|---|---|---|
supabase/lib/client_options.py | ClientOptions.replace | 8 ⭐ | 92 🙂 | 12 😞 | 58.64% 🙂 | Extract out complex expressions |
Legend and Explanation
The emojis denote the absolute quality of the code:
- ⭐ excellent
- 🙂 good
- 😞 poor
- ⛔ very poor
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!