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

Use the correct line tab #129

Open
vibern0 opened this issue May 18, 2019 · 7 comments
Open

Use the correct line tab #129

vibern0 opened this issue May 18, 2019 · 7 comments

Comments

@vibern0
Copy link

vibern0 commented May 18, 2019

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?

@paulinablaszk
Copy link
Contributor

It's a very good idea.
I think we should also change indentation in the code to be o be consistent with Solidity Style Guide -I've noticed that there are 4 spaces or 2 spaces used in different contracts. We can also convert all existing indentation to spaces

@vibern0
Copy link
Author

vibern0 commented Jul 23, 2019

Great, I'll open a PR.
Since you are working in #123 do you want to do that with the contracts?
I've realized there's no linter for JS either. Instead of editorconfig, maybe a linter is better, like eslint.

@paulinablaszk
Copy link
Contributor

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?

@vibern0
Copy link
Author

vibern0 commented Jul 23, 2019

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.
After that, we open another PR to fix this issue. 👍

@paulinablaszk
Copy link
Contributor

Sounds like a good plan :)

@abcoathup
Copy link
Contributor

Agree on updating the contracts once #123 is done.

My preference is consistency with OpenZeppelin contracts linting.

@xaler5
Copy link
Collaborator

xaler5 commented Dec 25, 2022

@obernardovieira does this still apply ?

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

No branches or pull requests

4 participants