-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Allow a generator to be provided instead of a List #1030
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1030 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 115 115
Lines 9238 9265 +27
Branches 2179 2190 +11
=========================================
+ Hits 9238 9265 +27 ☔ View full report in Codecov by Sentry. |
We need to properly support the |
But would this something you would support from an architecture point of view? |
Yes |
@tefra How would you like to proceed? Materialise List or Tuple in the tests? |
Testing it with my own code results in this error. So it is clearly not done yet.
|
Quality Gate failedFailed conditions |
Parsing breaks with Iterable.
|
1d77439
to
c99fbb9
Compare
Parsing solved. |
While it looked like 'working' again, I noticed that |
Quality Gate passedIssues Measures |
📒 Description
Considering you are writing a very big tree, you don't want to materialise that tree before it ends up in a file in a list first. Ideally the entire subtree should only be rendered just in time.
🔗 What I've Done
I have allowed a Generator to be handled as a List.
💬 Comments
There might be more places this needs to be changed. Since List[] is used everywhere, type hinting fails.
🛫 Checklist