Skip to content

Guilbertoliveira/AdministrativePanelTS

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

26 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Dashboard of patient

GitHub Language Count GitHub Top Language GitHub Pull Requests GitHub Contributors GitHub Last Commit Github License

🔨Project Status🔨

Project under improvement

Project description

project to improve my knowledge in typescript, a panel project to manage doctors' appointments, original project of alura's course

Improvements made to the project:

  1. Split files into styled components, placing in an individual file
  2. Installation of prettier in the project to improve code organization
  3. Code refactoring in english
  4. Tooltip improvements in design (style) charts
  5. Recharts payload improvements with tooltip (custom)
  6. Solving dynamic image bug

Version Mobile

Version Desktop

Technologies used

Project link

Link Vercel

Figma link

Link Figma

To use the project:

  1. Clone repository with gitbash
  2. https://github.com/Guilbertoliveira/AdministrativePanelTS.git
    
  3. To install project dependencies (you need to have node.js installed)
  4. npm install
    
  5. To run the project locally
  6. npm start
    
  7. Remembering that you need the backend that will be available, in this case the backend is "marked" in the file itself
  8. npm run api
    

Contributing

  • Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
  • Fork the Project
  • Create your Feature Branch (git checkout -b feature/AmazingFeature)
  • Commit your Changes (git commit -m 'Add some AmazingFeature')
  • Push to the Branch (git push origin feature/AmazingFeature)
  • Open a Pull Request

Conventional commits:

  • feat: (new feature for the user, not a new feature for build script)
  • fix: (bug fix for the user, not a fix to a build script)
  • docs: (changes to the documentation)
  • style: (formatting, missing semi colons, etc; no production code change)
  • refactor: (refactoring production code, eg. renaming a variable)
  • test: (adding missing tests, refactoring tests; no production code change)
  • chore: (updating grunt tasks etc; no production code change)