Philzen
Philzen
While upgrading to v2.0.0 and running the `yarn rw lint --fix` command, i bumped into one unfixable "error" and warning each. The error makes the command return an error code...
Make VSCode ignore the `.yarn`-folder and thus exclude it from parsing. Some more zen for the DX – and i guess some cpu cycles saved as VSCode won't try to...
Having installed yarn 3 globally (in home directory), running ~~~terminal yarn create redwood-app ./redwoodblog ~~~ fails with ~~~terminal ❯ Creating Redwood app ✖ Checking node and yarn compatibility Creating directory...
Using `postId` in the input for the createComment-test in `api/src/services/comments/comments.test.ts` gives the following red squiggle: ```bash Type '{ name: string; body: string; postId: number; }' is not assignable to type...
Just stumbled over this 404 on https://redwoodjs.com/docs/graphql#the-root-schema
### What's not working? During working on #6061 (where i wanted to fix some non-autofixable ESLint violations that came up during a 2.x upgrade), i initially fixed the ESLint warning...
While trailing whitespace is just bit noise in code (well, 99 % of the time...), for markdown it has actual signifiance. This used to drive me crazy for a while...
I was just revisiting the tutorial (which i can see has had some nice evolution and really useful additions) and wanted to upgrade the RedwoodJS stack as storybook just didn't...
### What's not working? Upgrading an existing project from v1.5.1 to latest (v2.1.1) via `yarn rw upgrade`, i got:  Apart from the fact that the word "communit" could clearly...
The CLI doc explicitly lists the `--open` command option and does not make any statement about this happening anyways – which tells me as a reader that it won't automatically...