Skip to content

Commit

Permalink
Refactor code style and naming conventions
Browse files Browse the repository at this point in the history
  • Loading branch information
bigint committed Nov 12, 2024
1 parent 0838170 commit 85280b6
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion .cursorrules
Original file line number Diff line number Diff line change
Expand Up @@ -79,5 +79,9 @@ Follow these rules when you write code:
- Write concise, technical TypeScript code with accurate examples.
- Use functional and declarative programming patterns; avoid classes.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., `isLoading`, `hasError`).
- Use camelCase for variables, functions, and methods.
- Use UPPERCASE for environment variables.
- Start each function with a verb, Example: `handleClick`, `handleKeyDown`, `handleChange`, etc.
- Use verbs for boolean variables. Example: `isLoading`, `hasError`, `canDelete`, etc.
- Use complete words instead of abbreviations and correct spelling.
- Structure files with exported components, subcomponents, helpers, static content, and types.

1 comment on commit 85280b6

@vercel
Copy link

@vercel vercel bot commented on 85280b6 Nov 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Successfully deployed to the following URLs:

web – ./

web-heyxyz.vercel.app
web-git-main-heyxyz.vercel.app
heyxyz.vercel.app
hey.xyz

Please sign in to comment.