Anime Tracker is a web application that allows you to track your favorite anime and manga.
- User/Admin Account
- Login
- Register
- Forgot Password
- Reset Password
- Change Password
- Change Email
- Delete Account
- Language
- Theme
- Light
- Dark
- System
- Custom
- Kimetsu no Yaiba
- Jujutsu Kaisen
- Naruto
- One Piece
- Dragon Ball
- My Hero Academia
- Hunter x Hunter
- Bleach
- Attack on Titan
- Profile
- Viewing Time
- Rank
- Achievements
- Avatar
- Display top 3/5/10 previously watched animes
- 3 recommendations of animes
- Mini Calendar
- List of animes
- Anime selection etcβ¦
- Watchlist / Favorites
- Achievements
- Rank
- Search
- Notifications
Work in progress
git clone [email protected]:kbrdn1/Anime-Tracker.git
cd app
bun install
bun dev
open http://localhost:5173
cd back
bun install
docker-compose up -d
bun dev
open http://localhost:3000
Use the following prefixes for your branch names:
feature/#<issue-number>-<feature-name>
bugfix/#<issue-number>-<bugfix-name>
hotfix/#<issue-number>-<hotfix-name>
chore/#<issue-number>-<chore-name>
refactor/#<issue-number>-<refactor-name>
test/#<issue-number>-<test-name>
docs/#<issue-number>-<docs-name>
feature/#1-add-new-feature
bugfix/#2-fix-typo
hotfix/#3-fix-bug
Use the following prefixes for your pull request titles:
[#<issue-number>] <pull-request-title>
[#1] Add new feature
Use the following prefixes for your commit messages:
<emoji> <type>(<scope>)<!>: <subject>
Use the following emoji prefixes for your commit messages Gitmoji
You can install the Gitmoji extension for VSCode here
Choose a type from the following list, in terms of the kind of change that you're committing:
feat
: A new featurefix
: A bug fixdocs
: Documentation only changesstyle
: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)refactor
: A code change that neither fixes a bug nor adds a featureperf
: A code change that improves performancetest
: Adding missing or correcting existing testschore
: Changes to the build process or auxiliary tools and libraries such as documentation generation
Choose a scope from the following list, in terms of the location of the change:
app
back
Any breaking changes should be indicated with !
after the type/scope. e.g. β¨ feat(back)!: this is a breaking change
- Describe what you did in imperative mood, e.g.:
Word Description Example add
Create a capability e.g. feature, test, dependency. β¨ feat: add new feature
change
Change behavior of the code e.g. refactor, style, doc. π§ chore: change config
remove
Delete a capability e.g. feature, test, dependency. π₯ feat: remove feature
fix
Fix an issue e.g. bug, typo, accident, misstatement. π fix: fix typo
bump
Increase the version of something e.g. dependency. β¬οΈ chore: bump version
make
Add or change something to make it work. π chore: make build
start
Begin doing something; e.g. create a feature flag. π chore: start feature flag
stop
End doing something; e.g. remove a feature flag. π chore: stop feature flag
optimize
A change that MUST be just about performance, e.g. speed up code. π chore: optimize code
revert
Revert a change e.g. revert commit. βͺ chore: revert commit
clean
A change that MUST be just about removing code. π§Ή chore: clean code
disable
A change that MUST be just about disabling code. π chore: disable code
refactor
A change that MUST be just about refactoring code. β»οΈ chore: refactor code
update
A change that MUST be just about updating code. π chore: update code
improve
A change that MUST be just about improving code. π chore: improve code
clean
A change that MUST be just about cleaning code. π§Ή chore: clean code
optimize
A change that MUST be just about optimizing code. π chore: optimize code
Source: Conventional Commits
- Don't capitalize first letter
- No dot (.) at the end
β¨ feat(app): add new feature
π fix(app): fix typo
π§ chore(app): change config
π₯ feat(app)!: remove feature
Versioning is done automatically by GitHub Actions
<major>.<minor>.<patch>
major
: Breaking changesminor
: New featurespatch
: Bug fixes
1.0.0
First release1.1.0
New feature1.1.1
Bug fix
.
βββ app
βΒ Β βββ src
βΒ Β βΒ Β βββ assets
βΒ Β βΒ Β βββ components
βΒ Β βΒ Β βΒ Β βββ containers
βΒ Β βΒ Β βΒ Β βββ layouts
βΒ Β βΒ Β βΒ Β βββ forms
βΒ Β βΒ Β βΒ Β βββ typography
βΒ Β βΒ Β βββ constants
βΒ Β βΒ Β βββ hooks
βΒ Β βΒ Β βββ pages
βΒ Β βΒ Β βββ router
βΒ Β βΒ Β βΒ Β βββ security
βΒ Β βΒ Β βββ stores
βΒ Β βΒ Β βΒ Β βββ contexts
βΒ Β βΒ Β βΒ Β βββ providers
βΒ Β βΒ Β βββ styles
βΒ Β βΒ Β βββ types
βΒ Β βΒ Β βββ utils
βΒ Β βΒ Β βββ App.tsx
βΒ Β βΒ Β βββ main.tsx
βΒ Β βΒ Β βββ vite-env.d.ts
βΒ Β βΒ Β βββ index.html
βΒ Β βββ .env.example
βΒ Β βββ .eslintrc.cjs
βΒ Β βββ .gitignore
| βββ .prettierignore
βΒ Β βββ index.html
βΒ Β βββ package.json
βΒ Β βββ panda.config.ts
βΒ Β βββ postcss.config.ts
| βββ .prettierignore
βΒ Β βββ prettier.config.mjs
βΒ Β βββ README.md
βΒ Β βββ tsconfig.json
βΒ Β βββ tsconfig.node.json
βΒ Β βββ vite.config.ts
βββ back
βΒ Β βββ prisma
βΒ Β βΒ Β βββ migrations
βΒ Β βΒ Β βββ schema.prisma
βΒ Β βΒ Β βββ seed.ts
βΒ Β βββ src
βΒ Β βΒ Β βββ constants
βΒ Β βΒ Β βββ controllers
βΒ Β βΒ Β βββ middlewares
βΒ Β βΒ Β βββ models
βΒ Β βΒ Β βββ routes
βΒ Β βΒ Β βββ services
βΒ Β βΒ Β βββ types
βΒ Β βΒ Β βββ utils
βΒ Β βΒ Β βββ index.ts
βΒ Β βββ .env.example
βΒ Β βββ .gitignore
| βββ .prettierignore
βΒ Β βββ docker-compose.yml
βΒ Β βββ package.json
βΒ Β βββ prettier.config.mjs
βΒ Β βββ README.md
βΒ Β βββ tsconfig.json
βββ .nvmrc
βββ .prettierignore
βββ prettier.config.mjs
βββ package.json
βββ README.md