When you double click on a folder name to rename it and then clicking off (without renaming it), the text bar should disappear and go back to the previous name. On new creation, placeholder text. On edit, normal text.

In files after refresh, unauthorised error when making request to api.

In the review page (web/src/pages/review/index.tsx), selecting a folder displays a list of 'accessed' flashcards. These are currently unselected by default and then appended to the 'selectedFlashcards' map when selected.
Instead, the functionality should be to select them by default. The folder, when selected, should append all flashcards to the map, and update them if they are deselected or reselected.

It might be useful to create a style guide for consistency in clarity as well as to serve as a useful reference.
Some possible points of discussion:

• Type naming conventions in requests/response (as mentioned by @jacob-horton )
  Currently types are defined in Rust and exported using ts-rs into web/src/types. We currently use XGet or XInsert to describe types passed to requests (GET or POST, respectively) but this convention is up for debate.

• CSS practices

A proposed system for something akin to encapsulation:

• When passing a className to a defined component, it should apply only to the outermost element and not contradict any other styles.
• I also think a set width, height, and display: block should be present on an element containing children passed in through props - this means children can be layed out by replacing the children passed with a <div className="w-full h-full"> without resulting in unexpected behaviour, say from using a flexbox or lack of.

return <div className={className ?? ""}> // no other styles here
    {someReactNode}
    <div className="w-full h-full">{children}</div> // block by default
</div>

• Component conventions?
  I have personally just been naming components based on what feels right and what the surrounding files have used.
  We write components as const Component = ({ propOne, propTwo }) => { ... } but this can easily be seen by looking at code in the repository.

• Tailwind style class ordering?
  As for me, I currently use something like flex size flex-parent-properties flex-child-properties styling (flex-parent-properties e.g. justify-content, align-items) (flex-child-properties e.g. align-self, grow, shrink). Formalising this could be pedantic, though.

• Prettier + ESLint