Skip to content
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

fix: add type check to client ci, remove type errors #880

Merged
merged 1 commit into from
Aug 1, 2023

Conversation

sgfost
Copy link
Contributor

@sgfost sgfost commented Aug 1, 2023

  • remove base class from tutorial API that didn't get fully implemented
  • remove TSX shim since this appears unused and causes compiler to complain

ref #878

- remove base class from tutorial API that didn't get fully implemented
- remove TSX shim since this appears unused and causes compiler to
  complain

ref virtualcommons#878
Copy link
Member

@alee alee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks @sgfost!

@sgfost sgfost merged commit dd64d3f into virtualcommons:main Aug 1, 2023
3 checks passed
@@ -128,7 +128,7 @@ deploy: build

.PHONY: buildprod
buildprod: docker-compose.yml
docker compose run --rm client yarn build
docker compose run --rm client yarn type-check-build
docker compose run --rm server yarn build
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a reason to not add type checking to the client's default yarn build (i.e., replace it instead of adding another command)

Copy link
Contributor Author

@sgfost sgfost Aug 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really, no. I did it this way so it doesn't actually run on a real deploy but that doesn't make a ton of sense since we'd want to fix anything before deploying. I'll switch them around

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants