burakcihan61 / typescript-master

TypeScript Design Patterns

Bu proje, TypeScript kullanarak yaygın tasarım desenlerini anlamak ve uygulamak için bir kaynaktır. Tasarım desenleri, yazılım geliştirme sürecinde karşılaşılan tekrar eden sorunlara karşı genel çözüm şablonlarıdır. TypeScript, güçlü bir statik tür sistemine sahip olduğu için, bu desenlerin uygulanması ve anlaşılması daha kolay hale gelir.

İçindekiler

1. Singleton Pattern
2. Factory Pattern
3. Observer Pattern
4. Decorator Pattern
5. Prototype Pattern
6. Builder Pattern
7. Facade Pattern
8. Proxy Pattern
9. Iterator Pattern
10. Adapter Pattern
11. Bridge Pattern
12. Composite Pattern
13. Flyweight Pattern
14. Command Pattern
15. Chain of Responsibility Pattern
16. Mediator Pattern
17. Memento Pattern
18. State Pattern
19. Strategy Pattern
20. Template Method Pattern
21. Visitor Pattern

TypeScript Tricks

1. Request Handler Axios

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

Learn More

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.
• Tailwind CSS Documentation - learn about Tailwind CSS features and API.
• Learn Tailwind CSS - an interactive Tailwind CSS tutorial.
• TypeScript Documentation - learn about TypeScript features and API.
• Learn TypeScript - an interactive TypeScript tutorial.
• React Documentation - learn about React features and API.
• Learn React - an interactive React tutorial.
• Learnd Markdown - an interactive Markdown tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

Commit-lint Types and Messages

Examples:

git commit -m "feat: add navbar component"

git commit -m "docs(readme): add server link"

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
• chore: Updating packages,build project etc. (no production code change)
• docs: Documentation only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that neither fixes a bug nor adds a feature, when refactoring a production code, eg. renaming a variable.
• revert: A commit revert message
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

License