prisma

When creating a cell, the test file reads:

import { render, screen } from '@redwoodjs/testing/web'

at the top. However, screen is unused in the generated test and thus ESLint complains:

'screen' is defined but never used. Allowed unused vars must match /^_/u.eslint[@typescript-eslint/no-unused-vars](https://typescript-eslint.io/rules/no-unused-vars)

Fun f

blitz b -> blitz build
blitz p -> blitz prisma
blitz c -> blitz console

etc

Let's move the CI over to Github Actions!

What happened?

from the entities page, when you navigate to an entity, the general setting tab is selected and you can see data,
but from the entity itself, when you want to navigate to a related entity, the related entity state is not set on the general settings tab.

What you expected to happen

I expect that the general setting tab would be selected while navigating from one e

Users can currently name their Wasp project using an arbitrary Wasp identifier:

The project's name must be a valid Wasp identifier:
  - It can start with a letter or an underscore.
  - It can contain only letters, numbers, or underscores.
  - It can't be a Wasp keyword.

However, our users have pointed out that this isn't flexible enough. For example, many people would like to name w

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