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

Jump to bottom

🛠️ Refactor: Add Code quality fixing scripts #65

Open
4 tasks
ArsalaBangash opened this issue Oct 20, 2020 · 0 comments
Open
4 tasks

🛠️ Refactor: Add Code quality fixing scripts #65

ArsalaBangash opened this issue Oct 20, 2020 · 0 comments
Labels
Domain: Dev Experience This issue pertains to a developer's emotions and attitudes when building Grey Software. hacktoberfest-accepted Role: Software Engineer Uses technology to design, develop, test, and maintain creative software solutions. Type: Maintenance An issue that make things clearer or removes ambiguity without changing base functionality.

Comments

@ArsalaBangash
Copy link
Member

Motivation 🏁

Our developers need an easy way of fixing code quality issues.

Describe your refactoring solution 🛠️

I propose adding code quality fixing scripts to our package.json, so our devs can simply run the following commands:

yarn fix
OR
yarn fix:js
OR
yarn fix:css

Additional details ℹ️

  • Use an eslint config file for code errors and warnings
  • Use a prettier config file for code style
  • Use stylelint for css
  • Add fixing scripts to the package.json file

Consult the futurist network repo for an example implementation
@ArsalaBangash ArsalaBangash added Domain: Dev Experience This issue pertains to a developer's emotions and attitudes when building Grey Software. Type: Maintenance An issue that make things clearer or removes ambiguity without changing base functionality. Role: Software Engineer Uses technology to design, develop, test, and maintain creative software solutions. labels Oct 20, 2020
This was referenced Oct 20, 2020
Open
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Domain: Dev Experience This issue pertains to a developer's emotions and attitudes when building Grey Software. hacktoberfest-accepted Role: Software Engineer Uses technology to design, develop, test, and maintain creative software solutions. Type: Maintenance An issue that make things clearer or removes ambiguity without changing base functionality.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ArsalaBangash