Skip to content
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

web: UI code pruning and clean up round #1 #1441

Merged
merged 38 commits into from
Jul 11, 2024
Merged

web: UI code pruning and clean up round #1 #1441

merged 38 commits into from
Jul 11, 2024

Conversation

dgdavid
Copy link
Contributor

@dgdavid dgdavid commented Jul 4, 2024

Problem

Switching from the former UI to the current approach left behind a lot of things to review, dead components and a CSS clean up among them.

Solution

Drop dead components and make as much clean-up rounds as needed. This can be considered Round #1, made in the middle of more urgent work.

Testing

Tested manually

Screenshots

Visual changes after this PR should keep at minimum. In any case, it's preferred that reviewers give the UI a shot taking the time they need.

@dgdavid dgdavid changed the title fix(web): stop using classNames for proposal actions web: CSS clean-up Jul 4, 2024
@dgdavid dgdavid force-pushed the css-clean-up branch 2 times, most recently from e910aac to 2b289d1 Compare July 5, 2024 08:05
Most likely they are no longer needed since (probably) 31aea73.
No longer needed since 951fe01.
Most probably dead since 726c632.
Dead since components clean-up made at 726c632
Dead since the wifi list selection removal at 1f80cd8.
It should be removed at de010da
Which contains rules no longer needed after changing the UI approach.
Probably related to 726c632
No longer used and somehow related with drops made at
2b289d1.
They were used for modifying the look&feel of some buttons, but they are
no longer needed.
Used in a no longer available dialog for selecting software patterns.
Related to 834a64d.
To make it fit in the new layout and avoid it crashing.
@dgdavid dgdavid changed the title web: CSS clean-up web: code pruning and clean up, round #1 Jul 11, 2024
@dgdavid dgdavid changed the title web: code pruning and clean up, round #1 web: UI code pruning and clean up, round #1 Jul 11, 2024
@dgdavid dgdavid changed the title web: UI code pruning and clean up, round #1 web: UI code pruning and clean up round #1 Jul 11, 2024
@dgdavid dgdavid marked this pull request as ready for review July 11, 2024 10:54
@dgdavid dgdavid merged commit cf5b82a into master Jul 11, 2024
2 checks passed
@dgdavid dgdavid deleted the css-clean-up branch July 11, 2024 11:34
dgdavid added a commit that referenced this pull request Jul 12, 2024
## Problem

The elements in the login page are rendered wrongly since
#1441. That's because the `Flex`
component used for wrapping the `core/EmptyState` children. It is
missing the "direction" prop for telling it to layout children
vertically instead of horizontally. Moreover, it looks like a `Stack`
element is a better choice for this case.

## Solution

Adapt `core/EmptyState` for using an `<Stack hasGutter>` instead of a
`<Flex>` configured to behave almost the same.

## Testing

- Tested manually
dgdavid added a commit that referenced this pull request Jul 29, 2024
Related to #1441, just another round of UI code improvements and clean
up.
dgdavid added a commit that referenced this pull request Sep 13, 2024
**Apart from a bit of clean up, this PR is intended for start writing
better core components** that has been on hold for a few months already.

It's the case of _core/Page_ component, which has been rewritten almost
for scratch and now makes the weird _core/CardField transitioning
component_ obsolete.


Please, note that this set of changes **continues with the migration to
TypeScript for touched files** and also **introduce a PatternFly/Flex
wrapper** in order to ease the work with its responsive props. It's a
bit complex because the (ab)use of advanced types but it does the job
without introducing props unknown by PF/Flex. As said in the file
comments, ideally

> would be better to add these responsive props shortcuts direclty in
PF/Flex to allow the consumer to just set the `default` value when not
needed to change it depending on the breakpoint. But at this moment
we're a bit short of time for creating and testing such an elaborated PR
against upstream.

---

Related to #1441 and
#1494
@imobachgs imobachgs mentioned this pull request Sep 20, 2024
imobachgs added a commit that referenced this pull request Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants