-
Notifications
You must be signed in to change notification settings - Fork 4
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
Refactor layouts #1500
Open
joonatank
wants to merge
42
commits into
main
Choose a base branch
from
refactor-layouts
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Refactor layouts #1500
Conversation
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
joonatank
force-pushed
the
refactor-layouts
branch
13 times, most recently
from
November 14, 2024 07:45
ac78065
to
412c44a
Compare
joonatank
force-pushed
the
refactor-layouts
branch
from
November 14, 2024 11:13
742e174
to
b9bfd05
Compare
There is a single page: customer front page that uses the large style so add $large variable for that.
- remove: unused styles - remove: duplicated code from reservations - remove: duplicated spinner code
- refactor: webstore reservation confirmation - refactor: success page to use SSR for redirect - refactor: cancel payment page to use SSR - remove: unnecesary useOrder hook
- fix: layout issues on mobile - use styled components over classes
fix: layout padding inconsistencies on mobile fix: global styling (tab wrapper)
joonatank
force-pushed
the
refactor-layouts
branch
from
November 14, 2024 11:27
b9bfd05
to
fa92da2
Compare
vincit-matu
reviewed
Nov 15, 2024
Comment on lines
+62
to
+69
$justify?: | ||
| "center" | ||
| "flex-start" | ||
| "flex-end" | ||
| "space-between" | ||
| "space-around" | ||
| "space-evenly"; | ||
$align?: "center" | "flex-start" | "flex-end" | "baseline" | "stretch"; |
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.
This doesn't take into account whether justify
/align
is for content
or for items
. All combinations of these are quite often used. Should the variable names maybe be justifyContent
and alignItems
- to leave room for justify-items
/align-content
?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🛠️ Changelog
Pages are now defined as a
flex
base layout, more complex pages addgrid
wrapper inside the flex to control two columns. Anything that is not a general purpose component is expected to primarily export fragments not divs and allow the page layout handle margins.flex
/grid
with gaps over custompadding
andmargin
per component.common/styles/util
includingFlex
component that should solve most basic use cases.common/styles/global.scss
instead of random places.$legacy
attributes fromH
components.<H2 as="h1">
h1
should stay consistent unless there is very specific case (ex. front page hero section).admin-ui
🧪 Test plan
🎫 Tickets