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.

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

refactor: added Prettier on entire codebase #404

Closed
wants to merge 2 commits into from

Conversation

Queen-codes
Copy link

Description

  • Run Prettier to format all code in the codebase
  • Add .prettierrc configuration file to set code formatting options

Related issue(s)

Screenshot 2023-03-14 at 18 06 04

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

Copy link
Member

@KhudaDad414 KhudaDad414 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Queen-codes We are using node 18 for this project. can you please regenerate your package-lock.json with that version?

@Queen-codes
Copy link
Author

@Queen-codes We are using node 18 for this project. can you please regenerate your package-lock.json with that version?

alright, would do this. Thank you very much

@sonarcloud
Copy link

sonarcloud bot commented Mar 16, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 3 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@Queen-codes
Copy link
Author

@Queen-codes We are using node 18 for this project. can you please regenerate your package-lock.json with that version?

HI @KhudaDad414 . Already did this. Please kindly review and confirm if I need to make any changes again.

@KhudaDad414
Copy link
Member

KhudaDad414 commented Mar 16, 2023

@Queen-codes thanks, as I see the package-lock.json version 3 is generate which I was not expecting. 🤔

@derberg Node 18 is being shipped with npm version 9 which generates the package-lock.json version 3.
can our CI/CD handle this or should we go back to node 16/14? 🤔

@Queen-codes
Copy link
Author

@Queen-codes thanks, as I see the package-lock.json version 3 is generate which I was not expecting. 🤔

@derberg Node 18 is being shipped with npm version 9 which generates the package-lock.json version 3. can our CI/CD handle this or should we go back to node 16/14? 🤔

Hi, sorry for the late reply. Is there anything I can do to help?

Copy link
Member

derberg commented Mar 21, 2023

@KhudaDad414 we didn't yet solve the problems of v1 and v2 and you are telling me there is v3 😆

@KhudaDad414
Copy link
Member

hey @Queen-codes can you use node 16 to regenerate package-lock.json and resolve the conflicts?

@Queen-codes
Copy link
Author

hey @Queen-codes can you use node 16 to regenerate package-lock.json and resolve the conflicts?

yeah, sure. thank you

@KhudaDad414
Copy link
Member

@Queen-codes The support for v3 is here and I think it's time to merge this. please let me know when you resolve the conflicts so we can merge this. thank you. 😄

@KhudaDad414
Copy link
Member

Hi @Queen-codes, do you need some help here?

@Souvikns
Copy link
Member

@KhudaDad414 I will be closing this as we already added prettier and I don't see any response in this PR.

@Souvikns Souvikns closed this Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

add prettier configuration
4 participants