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

The redwood.toml web.apiURl value is expected to accept any "absolute path (thats starts with /) or an absolute URI that starts with `http[s]://"

However, if I set web.apiUrl="/" I get the following behavior:

• local api and web server start successfully
• endpoint error

console log:

[Error] A server with the specified hostname could not be found.
[Error] Fetch API cannot load

What do you want and why?

If a user has a react-final-form with a JS Set (or Map) in the initial values, the form resets on some activities, e.g. switching to another tab.

Possible implementation(s)

This can be fixed by using the initialValuesEqual prop:

import deepEqual from "fast-deep-equal"

    <FinalForm
      initialValues={initialValues}
      initialValues

Let's move the CI over to Github Actions!

What happened?

The close button should be on top of the text.

What you expected to happen

1. Title should be - 14px bold
2. Commit message box should

There was a latent bug which was recently discovered by end-to-end testing as we were optimizing the writing of FileDrafts during the generation process. We had two different functions that were generating a server/src/server.js file. It was not noticed before as the correct one must have been always written last. When switching to a Map-based implementation with paths as the key, we collapsed

Problem

We could improve the readability / experience reading through the library source code if there were module level docstrings.

Suggested solution

All python modules should include a docstring explaining