fix: Split kwargs passed to gitlab client and graphql client#1151
fix: Split kwargs passed to gitlab client and graphql client#1151amimas merged 6 commits intogitlabform:mainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1151 +/- ##
==========================================
+ Coverage 87.14% 88.31% +1.16%
==========================================
Files 73 73
Lines 3461 3465 +4
==========================================
+ Hits 3016 3060 +44
+ Misses 445 405 -40
🚀 New features to boost your workflow:
|
589ba7a to
0c43a70
Compare
amimas
left a comment
There was a problem hiding this comment.
Thank you so much for looking into this. I only have one concern about maintaining a hard coded list of attributes for an external library. This is probably okay as a last resort. Would you be able to explore other alternatives?
I'm not experienced enough to suggest required code changes but left a comment below with a suggestion. Please take a look and let me know your thoughts or if you could try it out.
amimas
left a comment
There was a problem hiding this comment.
Looks good. Thank you again for the quick fix. I'll merge it now and will look into releasing this soon along with the original feature you've contributed.
Linked to #1140
Problem: Turns out python-gitlab dont pass kwargs to the graphql client, some kwargs would crash the init of the client.
Solution: Added explicit parameter whitelists in GitlabWrapper to pass parameters to the gitlab client or the graphql client
I have tested setting max_retries against a personnal gitlab instance and it worked. Dont know if an acceptance test would be useful here, let me know