prisma

Bug description

On windows, I run prisma format and note the unusual file ending. The lines are all LF, but the very last line is CRLF.

This causes issue on my Linux CI where it formats it ending in LF's only, causing a diff to occur and the build to fail.

How to reproduce

1. On windows do prisma format
2. Open in HxD or similar
3. See attached:

![image](https://user-images.g

Updated Issue

The below issue was caused because the file was not named [...auth].js, it was named something like passport.js. And in this case auth is not a dynamic param and so req.query.auth is undefined.

We need to provide helpful error in these two cases:

1. req.query.auth not defined - page must be named [...auth].js/ts
2. req.query.auth is defined, but not array - p

Continued from this reference PR #1773

Via a command like yarn rw setup command-alias, use Shadowenv to run redwood commands with just rw dev (for example). This setup command should:

1. add .shadowenv.d/rw.lisp
2. console output the installation steps and link to Shadowenv Doc

See commen

Let's move the CI over to Github Actions!

Is your feature request related to a problem? Please describe.
The User object is available using the @userdata decorators in GraphQL. Also, it is available as part of the request object.
This is not the current case with REST API - but it should.

Describe the solution you'd like
Make sure the User object is available on the request, also consider adding a @userdata decorator for

Here is an example of it being used: https://github.com/wasp-lang/wasp/blob/master/waspc/examples/todoApp/todoApp.wasp#L4 .

app todoApp {
    title: "ToDo App",
    head: [
        "<link rel=\"stylesheet\" href=\"https://fonts.googleapis.com/css?family=Roboto:300,400,500&display=swap\" />"
    ]
}

We should add short mention of it + description under: https://github.com/wasp-