- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.4k
          Rename todoApp to kitchen-sink and move it to examples/ dir
          #3197
        
          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
| Deploying wasp-docs-on-main with   | 
| Latest commit: | 8c08815 | 
| Status: | ✅ Deploy successful! | 
| Preview URL: | https://ffe9e5ee.wasp-docs-on-main.pages.dev | 
| Branch Preview URL: | https://franjo-todoapp-renaming.wasp-docs-on-main.pages.dev | 
| Nice stuff! I will let @infomiho approve since he knows this part better, but I support the change, and PR description sounds reasonable to me, so soft approve from me :D. | 
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 think it makes sense and the changes look OK to me.
I'd say we are blocked by:
This will currently make it so we don't run kitchen-sink tests on each PR.
I'd merge this only AFTER we implement the change that will run example apps tests on each PR, so we are not in a limbo with PRs that are not running tests on the kitchen-sink app.
Let me know if you need help with generating any of the production API keys for the kitchen sink app.
# Conflicts: # .github/workflows/ci-examples-test.yaml # .github/workflows/release-examples-deploy.yaml # waspc/ChangeLog.md # waspc/examples/todoApp/README.md # waspc/run
# Conflicts: # .github/workflows/ci-deploy-test.yaml

Fixes #3085
The goal is to make
todoAppmore public and accessible to users.For that reason we are renaming it to
kitchen-sinkand moving it toexamples/(fromwaspc/examples/) dir.As such
kitchen-sinkbecomes one of our example apps and will be treated so.To go along with that, we are moving
kitchen-sinktests fromwaspc-ci.yamlworkflow toexamples-e2e-tests.yaml.Additionally, we are adding it as one of the
deploy-examples.ymloptions.NOTE:
This will currently make it so we don't run
kitchen-sinktests on each PR.HOWEVER, in our release post mortem we did declare that we will want to run
examples-e2e-tests.yaml(along with other test worklows) on each PR. So when we do removepathsfrom their PR triggers, this will go back to old behavior of runningkitchen-sinktests on each PR.In this PR I also:
kitchen-sink'sREADME.mdensure_app_compiles_and_builds.shscriptwasp build+tscrunscripttest:examplesnow includeskitchen-sinktest:kitchen-sinknpx playwright install --with-depstoplaywrightbased tests to make sure we have all the deps installedSidenote: It's really hard to check if I covered all
todoApprenames since our tutorial apps are also calledtodoApp. It's good that we are renaming because confusion.TODO: Generate
kitchen-sinkproduction API keys.