-
Notifications
You must be signed in to change notification settings - Fork 91
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
prettier
in package.json
calling forge fmt
#516
Comments
@zgorizzo69 can you clarify what exactly you think I should do for
I basically already handled this in my mega PR. Here's the commit with the latest change https://github.com/ubiquity/ubiquity-dollar/blob/91db6ed9376c7fe1480a9b063e44c94d61a583ac/packages/contracts/package.json |
I think this is causing the formatting errors for the solidity files. |
@pavlovcik Currently working on issue
Maybe try just using tab_width = 4 with the formatter. I believe it defaults to 2 |
This is assigned to me so don't worry about it. @FibrinLab we will not use |
/start |
Skipping |
/start |
Skipping |
mind unassing if not working on the issue? |
If you can follow up in a couple of days and there are no updates then we can assign you! |
I just follow up, it looks like assignee it's not working on it after all |
imma make a PR soon |
hey,
|
@pavlovcik im gonna push the changes to #681 |
Pls create a separate PR, no need to clutter #681 |
oh sure i reverted the PR gonna make a separate |
/unassign |
You have been unassigned from the bounty @AnakinSkywalkeer |
@molecula451 The time limit for this bounty is on Tue, 20 Jun 2023 15:58:51 GMT |
|
[ CLAIM 200 WXDAI ]
|
I just realized that this could be causing the discrepancy with the formatting. Because this task is named "prettier" it is possible that lint-staged is calling this instead of what we expect.
Originally posted by @pavlovcik in #417 (comment)
if we agree to keep prettier over forge fmt we need to :
1 - add the dev dependencies as stated above
2 - update the overrides section of the .prettierrc in the root folder
Originally posted by @zgorizzo69 in #417 (comment)
The text was updated successfully, but these errors were encountered: