-
Notifications
You must be signed in to change notification settings - Fork 19
@W-19434936@ feat: add performance mode flag #492
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -24,6 +24,10 @@ Name of a component to preview. | |
|
|
||
| Launch component preview without selecting a component | ||
|
|
||
| # flags.performance.summary | ||
|
|
||
| Open the component preview in performance mode | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In the short term, I would prefer to not codify performance mode in the CLI flags. I'm not in love with the name for performance mode and I don't know that its intuitive why I would run in performance mode vs not. This seems like more of an app metadata conversation - if we are previewing a root component for an app, we should show the preview in full screen mode. Would you be ok with just using an environment variable for now (which would still allow us to support the hackathon)?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm open to other names for the flag. This name stems from the nav item in the header of the default application page(which can also change). cc @marcelinollano I believe the CLI should be able to perform the same actions as the default application view. Today, the CLI can launch into the preview application with and without a selected component, but it cannot launch into the "performance" view. I agree the naming is a bit unintuitive, but there is value in being able to preview a component without the "preview application chrome", especially for large components. |
||
|
|
||
| # error.directory | ||
|
|
||
| Unable to find components | ||
|
|
@@ -40,9 +44,15 @@ Failed to parse component metadata at: %s | |
|
|
||
| Unable to find component with name: %s | ||
|
|
||
| # error.performance-client-select-conflict | ||
|
|
||
| Cannot use --performance flag when --client-select is enabled | ||
|
|
||
| # examples | ||
|
|
||
| - Select a component and launch the component preview: | ||
| <%= config.bin %> <%= command.id %> | ||
| - Launch component preview for "myComponent": | ||
| <%= config.bin %> <%= command.id %> --name myComponent | ||
| - Launch component preview for "myComponent" in performance mode: | ||
| <%= config.bin %> <%= command.id %> --name myComponent --performance | ||
Uh oh!
There was an error while loading. Please reload this page.
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.
What if I don't pass the "performance" flag? Would I be able to see the "performance" link by clicking on the "Performance" link?
Uh oh!
There was an error while loading. Please reload this page.
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.
Yes. The same operation is available in the header of the default page in the preview application.
This flag would save the user the extra step of navigating into "performance" mode" if that is their target destination.