8000 docs: update the frontend section by championshuttler · Pull Request #1880 · ignite/cli · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

docs: update the frontend section #1880

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

Merged
merged 1 commit into from
Dec 14, 2021
Merged

Conversation

championshuttler
Copy link
Contributor

Fixes #1829

barriebyron
barriebyron previously approved these changes Dec 3, 2021
Copy link
Contributor
@barriebyron barriebyron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

docs/kb/serve.md Outdated
@@ -62,7 +62,7 @@ Reset the state only once. Use this flag to resume a failed reset or to initiali

Reset state on every file change. Do not import state and turn off state persistence.

`--rebuild-proto-once` use with `--reset-once`
`starport generate vuex`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`starport generate vuex`

I think we should just remove this from the serve command doc. It's a separate command now.

docs/kb/serve.md Outdated
@@ -62,7 +62,7 @@ Reset the state only once. Use this flag to resume a failed reset or to initiali

Reset state on every file change. Do not import state and turn off state persistence.

`--rebuild-proto-once` use with `--reset-once`
`starport generate vuex`

Force code generation from proto files for custom and third-party modules. By default, Starport statically scaffolds files generated from Cosmos SDK standard proto files, instead of generating them dynamically. Use this flag to perform code generation on all modules if a blockchain was scaffolded on an earlier Starport version or after a Cosmos SDK upgrade.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Force code generation from proto files for custom and third-party modules. By default, Starport statically scaffolds files generated from Cosmos SDK standard proto files, instead of generating them dynamically. Use this flag to perform code generation on all modules if a blockchain was scaffolded on an earlier Starport version or after a Cosmos SDK upgrade.

This paragraph only makes sense in the context of the flags above.


`starport chain serve --reset-once --rebuild-proto-once`
`starport chain serve --reset-once`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`starport chain serve --reset-once`

You technically don't need to serve a chain to generate Vuex client.

@fadeev
Copy link
Contributor
fadeev commented Dec 8, 2021

Thanks for contributing, @championshuttler! ✨

Copy link
Contributor
@barriebyron barriebyron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for picking this up @championshuttler we appreciate your contributions!

@ilgooz ilgooz merged commit 51c162c into ignite:develop Dec 14, 2021
Jchicode pushed a commit to Jchicode/cli that referenced this pull request Aug 9, 2023
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

Successfully merging this pull request may close these issues.

docs: Update the frontend section
4 participants
0