I am going through the current Tutorials (I and II) with very fine comb, since couple weeks ago. It would help me to know the version of Tutorials - v0.45.0 at this moment to be displayed the learn.redwoodjs.com page) and to keep this version unchanged until the WA of Docs ends).
I order to be of most help, I will redo my testing / verification as soon as the docs version is announced. I also suggest that each tester defines the output of yarn rw info as this tester’s signature: (mine is this)
yarn rw info
yarn run v1.22.17
$ /Users/nik/dev/pacific-north/initialize/redwoodblog/node_modules/.bin/rw info
(node:65988) ExperimentalWarning: stream/web is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
OS: macOS 12.2.1
Shell: 5.8 - /bin/zsh
Node: 16.13.1 - /var/folders/y3/n2p741pj7vq9ckj9jrmlbp6m0000gn/T/yarn--1646585440471-0.3586255412744028/node
Yarn: 1.22.17 - /var/folders/y3/n2p741pj7vq9ckj9jrmlbp6m0000gn/T/yarn--1646585440471-0.3586255412744028/yarn
SQLite: 3.36.0 - /usr/bin/sqlite3
@redwoodjs/core: ^0.46.0 => 0.46.1
@dthyresson, I like your wallaby suggestion a lot and will use it immediately, not only in the context of Tutorial QA.
I also strongly advise testing (with the caveat that I respond with "don’s look at what I am doing, listen to what I am telling). This is probably my best chance ever to do what I am advising other to do, so thanks for the nudge.
In order to get better initialized to use Wallaby and tests, help me with the advice on how to move ahead with my current issue:
I typed in all of the code explained in Authentication section, and using the signup page, defined my ID (as email@example.com) and password (as AnnArbor2022), not getting any error indications.
Now trying to get authenticated via Login page, I am getting this:
The error message most likely coming from Login page, so my best approach is to used the debugger (the VSCode / Chrome combo), find my last line of code which triggers this error and then using bisection find where in RW run time this happens.
I do agree with you David that this type of error (me supplying possible erroneous input) should be reported better than what I am currently getting (object which’s findUnique I try to invoke being null)
As this might be a discussion interesting to many, please respond to my questions.
It’s a Prisma and database related error where somehow your this.dbAccessor or Prisma Client is not valid.
Have you generated the Prisma Client after modifying schema?
Does yarn rw prisma generate and restarting the dev server correct it?
I do not believe that I regenerated the Prisma client after modifying the schema - probably was interrupted following the tutorial steps and when returning, my own state (as managed in my head) was incorrect.
Equally important is this:
This actually shows me of an issue in error handling:
In GraphQL we’d mask this error to prevent you seeing it’s a Prisma related and a database error.
But, since this is serverless function, these errors aren’t masked nicely Sio sensitive info can leak.
I do not want to continue this discussion under the topic “Help QA the new & improved Tutorial!”, as this subject is a lot more general. So, I will make a note in my own log being kept in “Tutorial QA” and will resurface it at a better time
@giannelli.tech - my direct response to your RW tutorials QA invitation is written here to avoid pollution of your original invitation to start the QA. As you will see, I created a more structured approach using my QA Github repo, which will allow me to share my code with other tester’s code.