-
Notifications
You must be signed in to change notification settings - Fork 46
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
feat(storage): configure boot #1808
Merged
joseivanlopez
merged 17 commits into
agama-project:storage-config-ui
from
joseivanlopez:storage-boot-model
Dec 20, 2024
Merged
Changes from 1 commit
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
6043d7b
fix(schema): use alias for boot device
joseivanlopez b5213c8
fix(storage): get boot device from alias
joseivanlopez eb3c5e1
chore(storage): split config checker
joseivanlopez 02be420
feat(storage): check boot config
joseivanlopez 35b6199
chore(storage): reorganize config solvers
joseivanlopez 06fc6c0
feat(storage): extend boot config
joseivanlopez 1ee52ea
feat(storage): add boot config solver
joseivanlopez fe10bce
fix(storage): avoid error in the old proposal settings
joseivanlopez e9036dc
feat(schema): add support for boot in storage model
joseivanlopez 24ddb84
feat(storage): add boot to config model
joseivanlopez fe814ee
feat(web): update config-model types
joseivanlopez 1401724
feat(web): extend and unify config model hooks
joseivanlopez d807efe
fix(web): adapt to new config model hooks
joseivanlopez cbf0d39
feat(web): allow changing boot options
joseivanlopez a108175
feat(storage): use proper space policy
joseivanlopez b12898a
fix(storage): use securerandom to generate aliases
joseivanlopez ce3e1e9
Fix typo
joseivanlopez File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
A question for @dgdavid
When we navigate to page for defining a custom policy to find space, the title and subtitles are
When we navigate to the boot options, they are:
Both are fine to me. But I wonder whether they should follow a more similar schema. I mean, the first one is explicitly exhorting the user to do something while the other is explaining where we are and what it means.
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.
Good point!
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.
Anyway, this is not a blocker for merging. Let's do a demo at the next review meeting that discuss those details afterwards.
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'm more for going to the second approach: let the user know where they are and what can do there.
That said, unless I have not strong opinion right now, it looks perfectly fine to me to now follow/force an schema just because. If it is better to use a different approach in a very specific page, why not? It will be better than providing nor enough informatio.
In any case, I fully agree with you on not blocking the PR for this and letting titles evolve with the rest of development. Do not forget that most probably Agama will end up getting breadcrumbs at some point, which can make us to rethink these texts.