-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Update generation code for the specific case of geojson #463
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #463 +/- ##
=======================================
Coverage 78.06% 78.06%
=======================================
Files 101 101
Lines 4149 4149
Branches 1185 1185
=======================================
Hits 3239 3239
Misses 910 910 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great!
General points:
- Maybe the file needs to be updated to make clear that it is generating TypeScript.
- I didn't try to run it. Is there any kind of CI in place to validate the output of this script? For example, to ensure that the TypeScript it generates is valid?
Co-authored-by: Bart Louwers <bart.louwers@gmail.com>
Yes, this is a pre-build script to generate typescript files from the v8 json spec file, these files are then used to build the package and are checked during the typescript transpilation. |
Please propose what you think might help here.
|
Ok, one last PR that I need to handle before releasing a new version which is currently stale and I need to rewrite myself. |
Launch Checklist
Fixes #393
This add an ugly if to the code generation flow to facilitate the fact that the json definitions are not full enough to represent the
data
field in theGeoJSONSourceSpecification
.It's a very small fix and I think it adds a lot of value, so I can live with it being dirty I guess...
before:
After
CHANGELOG.md
under the## main
section.