feat: enforce lowercase primitive type names #144
+46
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The docs are inconsistent in type names (90% string, 10% String, similar for number vs Number, etc). The eventual
electron.d.ts
output gets them finally converted tostring
andnumber
, but let's throw an error if the titlecase ones are used in the docs to better enforce consistency and avoid user confusion.A consequence of this change is a lot of types in
electron-api.json
are currentlyString
, and they'll all becomestring
- I think that should be fine.