-
Notifications
You must be signed in to change notification settings - Fork 147
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
avoid $
at begging in ```sh codeblocks, require codeblock have language
#358
base: main
Are you sure you want to change the base?
Conversation
cargo run -p graph-node --release -- \ | ||
--postgres-url postgresql://USERNAME[:PASSWORD]@localhost:5432/graph-node \ | ||
--ethereum-rpc NETWORK_NAME:[CAPABILITIES]:URL \ | ||
--ipfs 127.0.0.1:5001 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
--ipfs 127.0.0.1:5001 | |
--ipfs 127.0.0.1:5001 \ |
i think?
📦 Next.js Bundle Analysis for @graphprotocol/docsThis analysis was generated by the Next.js Bundle Analysis action. 🤖 Ten Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored. |
"prettier": "prettier . --loglevel warn --write", | ||
"prettier:check": "prettier . --loglevel warn --check", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I previously added --loglevel warn
because it lists all the files otherwise, even the ones that are correctly formatted, and I felt like it was uselessly verbose. Do you like that behavior, or does adding --cache
and --list-different
change it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, so I just realized that --loglevel warn
was only necessary if --check
wasn't present (my bad for missing that), and that --list-different
basically does the same thing, but it's even better because it looks like something's happening by updating that last line like you said. Awesome, thank you!
fixes #350