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

Post Implement Custom Lint work #1584

Closed
7 tasks done
literalEval opened this issue Feb 27, 2023 · 10 comments · Fixed by #1634
Closed
7 tasks done

Post Implement Custom Lint work #1584

literalEval opened this issue Feb 27, 2023 · 10 comments · Fixed by #1634
Labels
feature request unapproved Unapproved, needs to be triaged

Comments

@literalEval
Copy link
Member

literalEval commented Feb 27, 2023

Bugs

  • Get flutter pub get to run inside talawa_lint
  • Upgrade or remove explicitly mentioned Dart version in push.yaml (Remove only if it can be proved that explicit definition is not doing anything special)

Core Implementation

  • Add ignore directive corresponding to our new custom lint rules at the beginning of each file.
  • Add a script that will check for the presence of our ignore directive in entirety of a file and
    • Pass if ignore directive is not found anywhere
    • Fail otherwise
  • Add flutter pub run custom_lint in the workflow so that our custom lint rules are actually checked for during pull request and push.
@github-actions github-actions bot added the unapproved Unapproved, needs to be triaged label Feb 27, 2023
@literalEval
Copy link
Member Author

@palisadoes

Screenshot_20230227_213101

I am able to check our custom lint rules in the workflow 🎊

@palisadoes
Copy link
Contributor

  • This is good news, steady progress.
  • Where are you planning on documenting this? We may need a separate style guide external to contributing.md and link between the two.

@literalEval
Copy link
Member Author

Yeah. I believe we should add it's documentation in our docs site and refer to it in Contributing.md

@palisadoes
Copy link
Contributor

@literalEval What's the progress on this an the related open issues?

@literalEval
Copy link
Member Author

literalEval commented Mar 6, 2023

Will try to create a new PR till night @palisadoes . Sorry, was busy travelling.

@palisadoes
Copy link
Contributor

Happy Holi!

@literalEval
Copy link
Member Author

literalEval commented Mar 6, 2023

Same to you @palisadoes 🎊 🎊 :)

@literalEval
Copy link
Member Author

literalEval commented Mar 6, 2023

@palisadoes can you please stop merging new PRs from now on till I get the Add ignore statement to files task of this issue merged ? Reason for this being that all of the dart files will be modified and may cause merge conflicts.
I will open the respective PR after your confirmation. Thanks.

@palisadoes
Copy link
Contributor

OK

@palisadoes
Copy link
Contributor

@anwersayeed @tasneemkoushar This issue is nearing completion for forcing contributors to have valid DartDoc comments when submitting PRs. Please take a final look on #1479 to make sure that the formatting proposed in compatible with DartDoc.

This will hopefully improve the quality of our code over time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request unapproved Unapproved, needs to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants