feat: re-style the keyboard shortcuts menu #996
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#996
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/restyle-shortcuts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Before:
After:
I think this looks a lot cleaner now.
Hi konrad!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://996-featrestyle-shortcuts--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
@ -49,2 +49,3 @@
<style>
<style scoped>
dl {
Use classes and not tags to reduce specifity and make it possible to change tags without the need to change styles.
Of course we tried to make a good choice here with the tags, but you never know :)
Example:
Changed.
@ -53,0 +62,4 @@
margin-bottom: .5rem;
}
.message:not(:last-child) {
Can
.message
ever be a:last-child
? Seems like there should always be shortcuts below.Here it cannot, but the styling from bulma uses
.message:not(:last-child)
. This requires me to use the exact same thing if I want to override it, another possibility would be!important
but I think this one is a bit cleaner.=/ that's ugly.
Okay keep it for now.
I think we should create a message component either way.
Would remove a lot of duplication.
Then we can use own classes and don't need all the bulma stuff.
Oh yes, definitely. There's even a few variants of it in use already...
@ -53,0 +70,4 @@
padding: .75rem;
}
.keyboard-shortcuts {
Try to order classes by appearance in the template (makes it easier to follow when the component grows in size).
Done.
@ -53,0 +71,4 @@
}
.keyboard-shortcuts {
text-align: left;
This seems like a hack that is needed because the
modal.vue
currently doesn't provide a variant for this usecase.Seems like a valid usecase though.
Probably we should redo the modal at some point to remove these kind of hacks.
So this is fine for now?
Yes! =)