-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
fix: resolve eslint findings #54
Comments
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
Prettified code post-initial ESLint re #54
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 21, 2024
flamingquaks
added a commit
that referenced
this issue
May 22, 2024
flamingquaks
added a commit
that referenced
this issue
May 22, 2024
flamingquaks
added a commit
that referenced
this issue
May 23, 2024
…eans CLI had while(true) loops which have a higher risk of infinate loop. Replaced with variables. re: #54
flamingquaks
added a commit
that referenced
this issue
May 23, 2024
* Create eslint.yml to automate eslint findings in GitHub Actions * style(eslint): resolved style related findings for eslint * refactor(cli): changed while loops from constant true to dynamic booleans CLI had while(true) loops which have a higher risk of infinate loop. Replaced with variables. re: #54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: