Add complete typing stubs for pglast v8#191
Conversation
|
Thank you, seems good. OTOH, I'm (veeery slooowly) trying to improve the plpgsql support that |
|
Please try to rebase on current v8, the (main) CI error should solve. |
d49f1fd to
f16b403
Compare
|
Hi Alex, I'm not sure if that last commit, "Fix typehint runtime probes in CI" is actually needed, after commit 24c9b19. Can you clarify please? |
|
I merged v7 into v8 and pushed the result. Merging this comes next. |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## v8 #191 +/- ##
====================================
Coverage ? 0.00%
====================================
Files ? 23
Lines ? 7378
Branches ? 0
====================================
Hits ? 0
Misses ? 7378
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Generate stubs for AST, enum, keyword, and printer modules, add handwritten stubs for public modules, and wire stub generation and package data into the build. Add focused ty and mypy coverage for AST fields, parser results, streams, printers, and importable public modules.
1d878c7 to
8857f0e
Compare
yeah, I've reworked it to avoid the need for this |
For some reason I could not (yet) figure out, after the merge of PR #191 the coverage report started to emit "No data was collected (no-data-collected)", effectively listing all sources with 0% coverage...
|
Thanks a lot, I merged this into v8, with a couple of minor tweaks on top. |
3 participants
Hi - I'd like to get more extensive type stubs into pglast, Since I've not contributed to this project before please let me know if I'm on the right path here, or if you want a completely different approach