-
Notifications
You must be signed in to change notification settings - Fork 59
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
🚀 Feature: use linting tools (pre-commit) #60
Comments
I wonder if there is a common formatting being followed in sdk-generator for all SDKs using composer that's why we are not implementing something like this separately? |
I'm interested in implementing this feature. I agree that using linting tools like black, flake8, and isort can significantly improve the consistency of our code style. The pre-commit hook idea is also excellent as it can prevent unnecessary commits with incorrect formatting. I have experience working with these tools. Can someone please assign this task to me? |
Hey @jayanth-kumar-morem it's great that u want to contribute but just a suggestion that please don't tag the maintainers directly for getting assigned to some issue |
Okay, Alright, should I draft a PR then ? |
You should wait for someone to approve this first |
Oh, Alright @Ananya2001-an |
Thank you for opening this @Ananya2001-an - our SDKs are actually generated via https://github.com/appwrite/sdk-generator so it is an important consideration about where to add it, how to add it, automating it, etc so a deeper look at this is required. I will be looking into this and letting you know what the decision is. |
Sure @joeyouss :) |
Is this still open? |
🔖 Feature description
I think we can use famous linting tools like black, flake8 and isort to keep the code style consistent and maybe we can use
pre-commit
hook to make sure the format is correct before making any unnecessary commits.In some files like here:
sdk-for-python/appwrite/client.py
Line 1 in df27804
io
in this case which can be easily detected using something like this. We can use husky as well....We can also later on add a ci workflow to make sure lint tests pass. wdyt?
🎤 Pitch
We can use
pre-commit
as a dev dependency and create a .pre-commit-config.yaml file in the root dir like this:👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: