-
Notifications
You must be signed in to change notification settings - Fork 683
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
Use the correct line tab #129
Comments
It's a very good idea. |
Great, I'll open a PR. |
I can correct the contracts. Do you think I should do it within #123 or is it better to wait for the review to don't mix those issues? |
Let's not mix it. #123 is already really big and you've put a huge amount of time and really good work. And that is about migrating it to 0.5, so let's keep it this way. |
Sounds like a good plan :) |
Agree on updating the contracts once #123 is done. My preference is consistency with OpenZeppelin contracts linting. |
@obernardovieira does this still apply ? |
As I work with 4 spaces as a tab, I immediately saw the difference. I prefer the 4 spaces, but that is not the problem.
Since I use VSCode and, by default I have 4 spaces, the code I was writing, was not being formatted correctly.
In all my projects, I use EditorConfig. It will be awesome to have it here as well. What are your thoughts?
The text was updated successfully, but these errors were encountered: