-
Notifications
You must be signed in to change notification settings - Fork 8
feat(typesync): initial TypeSync implementation #175
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
Conversation
cmwhited
commented
May 5, 2025
- Initialize TypeSync app with Effect CLI template and Hono API
- Implement schema builder UI with browser approach
- Build app codegen layer and GraphQL integration
- Create app event/activity feed and details pages
- Implement command palette for types and apps search
- Setup SQL migrations and Effect/platform integration
- Build static and API router separation
- Add home page with apps grid and stacked list view
- Implement navbar integration with user-created apps
- Add schema validation and asset verification
- Initialize TypeSync app with Effect CLI template and Hono API - Implement schema builder UI with browser approach - Build app codegen layer and GraphQL integration - Create app event/activity feed and details pages - Implement command palette for types and apps search - Setup SQL migrations and Effect/platform integration - Build static and API router separation - Add home page with apps grid and stacked list view - Implement navbar integration with user-created apps - Add schema validation and asset verification
apps/typesync/.gitignore
Outdated
@@ -0,0 +1,17 @@ | |||
coverage/ |
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.
Nit pick: @fubhy cleaned up the repo once and moved all gitignore entries to the root gitignore. Can you do the same with this one? (not sure if there is even anything here we are not already covering in the root gitignore)
'eslint-plugin-react-hooks': '^5.2.0', | ||
'eslint-plugin-react-refresh': '^0.4.19', | ||
globals: '^16.0.0', | ||
prettier: '^3.5.3', |
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.
curious why prettier & eslint over biome? (not objection here, just curious)
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.
Just went with that since it and prettier are the defaults for vite+react. so trying to keep this as close to that experience. vs biome, which is what we decided for hypergraph. though not specifically tied to it
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.
makes sense, thanks for the explaination
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.
nice work!