-
Notifications
You must be signed in to change notification settings - Fork 32
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
Remove gap between sidebar boxes (for POIs) #2043
Conversation
Code Climate has analyzed commit 2b2ba3a and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 75.0% (0.0% change). View more on Code Climate. |
987d6e5
to
3f432d2
Compare
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.
Thank you for PR 👍 Looks very nice 😃
Do we need an entry in changelog?
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.
No gap now ✅
But there is a regression change:
If I collapse some blocks and re-open form, blocks are reordered randomly.
It's not reproduced on develop branch - all blocks always retain their position.
Do we want and can avoid it?
UPD. it should probably be a "comment", not a "change request". But I don't know if I can change it already 🙈
566640f
to
f17cf8e
Compare
Thank you for your reviews! @MizukiTemma I will add an entry to the changelog once I have extended this to events and pages :) |
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.
4a60374
to
b63a63c
Compare
Oh, good catch. I don't know why I didn't see this. The gap-2 is of course not working anymore. I should have thought of that. I think it's fixed now :) |
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.
b63a63c
to
a751d65
Compare
Very good catch. Thank you for the detailed feedback. In some parts this goes beyond what I wanted to do with this PR and in other parts I created this issue during a rebase. I adjusted the spacing for all boxes and gaps to class category 4 (e.g. gap-4 or mb-4, =1rem). I was only able to double check if my changes work for screens smaller than 2100px. For screens above 2100px I can only test it earliest next week |
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.
Looks good to me!
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.
Thanks! 👍
Now I cannot find anymore problems, looks good!
I would just reword the changelog entry.
584a748
to
2b2ba3a
Compare
Short description
With introducing the collapsible boxes to the page, event and POI form we created a gap between the boxes when certain boxes are collapsed. This is mainly due to two factors: a. using grid instead of flex, b. the two sidebars for medium and 4xl screens aren't wrapped inside one parent div. These changes are going to be relevant for all post types, however in this PR (at least up until now) I focused on POIs only. If we fixed everything for POI I will extend these changes to events and pages one by one.
For a graphical summary on what I tried to fix see the screenshots here:
Before:
After:
Proposed changes
Side effects
While testing this, I didn't run into any. However I can't imagine that there are now, since this is a major change. So I would ask you to test this PR thoroughly 😊
Please also check if you can find classes, that aren't used anymore, so I can remove them :)
Resolved issues
Fixes: Parts of #2032
Pull Request Review Guidelines