Add smoketests for template generation #4000
Open
Conversation
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
drogus
force-pushed
the
drogus/templates-tests
branch
from
97e90ea to
2ab9c36
Compare
We now specify the path in the template, similarly to what we do in quickstart-chat-rust, so no version change is needed.
bfops
added
release-any
drogus
force-pushed
the
drogus/templates-tests
branch
from
e1bcaad to
4b4f94b
Compare
…gus/templates-tests
This reverts commit ccf0ef2.
drogus
force-pushed
the
drogus/templates-tests
branch
from
23b4b2c to
bbb0638
Compare
drogus
force-pushed
the
drogus/templates-tests
branch
from
2e87244 to
cba8bfd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of Changes
Basic tests for templates, the test tries to generate each of the template, build and publish the SpacetimeDB part, and build or type check the client side.
This PR also includes bindings for all of the clients as it's needed for the tests to work and given the choices to either generate during the test run or include the bindings in git we chose the latter. This makes it consistent across the templates as some of them already included bindings.
Expected complexity level and risk
1