You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't need to be checking in all of the generated code, but we do want to ensure the most recent generated code in a few circumstances.
coinstacks/api/src/routes.ts does not need to be tracked. this is automatically generated on yarn build and kept up to date during development. We run yarn build and persist the workspace in CircleCI, so we will have the routes available for deployed image.
coinstacks/api/src/swagger.json should be tracked. There is currently a pre-push hook that runs generate, but it is easy to miss the update and merge without actually committing the most recent swagger. It would be ideal to pull this out so that on merge, we run generate on the project and commit any swagger changes before merge to ensure they are up to date in the repository.
packages/client/src/generated does not need to be tracked. We should set up a way to handle hot regeneration of the client for development. Right now publishing is manual, we will want to generate and publish this package after deployment of coinstacks.
The text was updated successfully, but these errors were encountered:
We don't need to be checking in all of the generated code, but we do want to ensure the most recent generated code in a few circumstances.
coinstacks/api/src/routes.ts
does not need to be tracked. this is automatically generated onyarn build
and kept up to date during development. We runyarn build
and persist the workspace in CircleCI, so we will have the routes available for deployed image.coinstacks/api/src/swagger.json
should be tracked. There is currently apre-push
hook that runs generate, but it is easy to miss the update and merge without actually committing the most recent swagger. It would be ideal to pull this out so that on merge, we run generate on the project and commit any swagger changes before merge to ensure they are up to date in the repository.packages/client/src/generated
does not need to be tracked. We should set up a way to handle hot regeneration of the client for development. Right now publishing is manual, we will want to generate and publish this package after deployment of coinstacks.The text was updated successfully, but these errors were encountered: