Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo in documentation #486

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix typo in documentation #486

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/maestro/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,6 @@ pnpm test:e2e

- [lib](/apps/maestro/src/lib/) libraries and application specific utilities
- [auth](/apps/maestro/src/lib/auth) auth utilities and hooks
- [drizle](/apps/maestro/src/lib/drizzle) drizzle setup
- [drizzle](/apps/maestro/src/lib/drizzle) drizzle setup
- [schema](/apps/maestro/src/lib/drizzle/schema) relational db schema
- [server](/apps/maestro/src/server/) tRPC routers/procedures
2 changes: 1 addition & 1 deletion apps/maestro/src/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Here's a brief description of each file and directory in the project:

> When designing an application, it's important to carefully consider the appropriate level of granularity for components, compounds, and features. Components should be small and focused, while compounds should be larger building blocks that are composed of smaller components. Features should be self-contained and independent from other parts of the application, with their own set of components and functionality. Following best practices for React patterns, MVVM, and feature-driven development can help ensure that your application is modular, scalable, and easy to maintain.

## Why unstated-next?
## Why Unstated Next?

Unstated Next is a small library that provides a simple and intuitive way to manage state in React applications using the context API. However, for more complex state management needs, other state-management solutions such as Jotai, Zustand, or XState may be more appropriate.

Expand Down