-
Notifications
You must be signed in to change notification settings - Fork 894
feat: Switch packages for typescript generation code #1196
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
ee71acd
feat: Switch packages for typescript generation code
Emyrk b0b17d0
Add enum functionality
Emyrk 28c2811
Handle reused types
Emyrk 710b427
Add comment
Emyrk 071026d
Allow ignoring types for autogen
Emyrk 2741efa
Fix ignore, add optional fields
Emyrk c62feeb
Add map support
Emyrk 462ebeb
Handle unknown types better
Emyrk 21d1687
Add comments, run gen
Emyrk 9a3d7e3
Add basic readme
Emyrk 1afaa5d
Merge remote-tracking branch 'origin/main' into stevenmasley/redo_typ…
Emyrk 7cfba41
Reorder imports
Emyrk 0127e6d
Sort all output
Emyrk 0d943f1
Add 'DO NOT EDIT' to the top
Emyrk 2379c21
Go linting
Emyrk 3865f36
Fix typescript linter
Emyrk 176b481
Use correct array size for allocation
Emyrk 0d37eeb
Update readme
Emyrk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Handle reused types
- Loading branch information
commit 28c2811acaa86d47e239ac79ee147a0d5ebde83b
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
We should focus on making this script work perfectly for what we already plan to do in
codersdk
. If this is relevant with that in mind, you should probably make this more specific to the code that handles this.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.
I don't know if we need it. This is really to match Go types, but the general error/response type is not bad to implement once in TS for all endpoints that use it.
I don't want to run this code on another package, and type inferencing across packages is only possible to an extent.
I removed the TODO, but the basic thing is that external types are not currently handled. The only way to handle them better, is to run this code on those packages as well. Obviously then we want to allowlist types, vs the current deny list approach.
Here is the example of external types:
http://github.com/coder/coder/blob/3865f36c4bf8c2ddfc1c9081cf7bbf1a881675f6/codersdk/templateversions.go#L27-L30
They use database types that include enums. I would like to have a conversation about how to handle these, as we can handle them. Just a matter of "how"