-
Notifications
You must be signed in to change notification settings - Fork 31
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
290 desktop client should not force user to setup a local core #324
base: dev
Are you sure you want to change the base?
290 desktop client should not force user to setup a local core #324
Conversation
✅ Deploy Preview for lodestone-dashboard ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for lodestone-storybook ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Co-authored-by: Kevin Huang <[email protected]>
Regarding back button, I think the default browser "navigate backward" behavior might be enough.
|
type="button" | ||
iconRight={faArrowLeft} | ||
label="Back" | ||
onClick={navigateBack} | ||
/> */} | ||
onClick={() => { |
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.
can this be shortened to onClick={navigateBack}?
return; | ||
} | ||
|
||
// if (coreList.length > 0) { |
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.
why is this redirect commented out?
Description
Added way for users to skip local core setup in initial page load in Tauri:
Added extra button in core select page in Tauri for local setup later on - this works by selecting the first option that shows up in Tauri, which might not work in all cases.
Type of change
Note: make sure your files are formatted with rust-analyzer