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

Fix: Fixing formating and linting across the website code #541

Closed
wants to merge 20 commits into from

Conversation

DhairyaMajmudar
Copy link
Contributor

What kind of change does this PR introduce?

Formats the code files.

Issue Number:
#539

Screenshots/videos:
N/A

If relevant, did you update the documentation?

N/A

Summary
Code files are now formatted

@DhairyaMajmudar DhairyaMajmudar requested a review from frouioui as a code owner May 1, 2024 04:55
@Gmin2
Copy link
Contributor

Gmin2 commented May 1, 2024

In my opinion we should add a script here that enforces linting and check on every new PR created through github actions,
And mentioned it in the contribuding guide to run the lint command before submitting a PR.
In this way we dont have to do this manually all the time, the actions will fail if the changes pushed does not have linting

cc @frouioui views?

@DhairyaMajmudar
Copy link
Contributor Author

That's indeed a very good idea if @frouioui approves add that implementation in the PR

@frouioui
Copy link
Member

frouioui commented May 2, 2024

I think we should do what @utnim2 mentioned

@DhairyaMajmudar
Copy link
Contributor Author

Sure will work on this 💯

@DhairyaMajmudar
Copy link
Contributor Author

@frouioui I have added the script npm run format using which the files can be formatted. Also updated the readme.md file : )

Copy link
Member

@frouioui frouioui left a comment

Choose a reason for hiding this comment

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

To come back on what @utnim2 was saying, I think we should make this a CI check on every PR just like what we have in .github/workflows/golang_lint.yaml.

@DhairyaMajmudar
Copy link
Contributor Author

To come back on what @utnim2 was saying, I think we should make this a CI check on every PR just like what we have in .github/workflows/golang_lint.yaml.

Sure looking forward to add lint CI

@DhairyaMajmudar DhairyaMajmudar requested a review from frouioui May 8, 2024 20:26
@@ -0,0 +1,53 @@
name: PR Workflow
Copy link
Member

Choose a reason for hiding this comment

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

The name of the workflow should be more descriptive 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah good catch : D

I have improved this in my recent commit.


jobs:
linting_and_type-checking:
name: Linting, Formatting and Type checking
Copy link
Member

Choose a reason for hiding this comment

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

The job name as well, we should mention it is related to react/ts

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done this one also : )

@DhairyaMajmudar DhairyaMajmudar requested a review from frouioui May 9, 2024 18:27
author Dhairya Majmudar <[email protected]> 1715198956 +0530
committer Dhairya Majmudar <[email protected]> 1716135857 +0530

fix

adding format script and updating readme

updating readme

work dir fix

work dir fix

fix

workdir

removing commit
@DhairyaMajmudar
Copy link
Contributor Author

Moving changes to PR #545

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.

3 participants