feat(web): Migration to PatternFly v6, round 1#1900
Merged
dgdavid merged 36 commits intostorage-config-uifrom Jan 16, 2025
Merged
feat(web): Migration to PatternFly v6, round 1#1900dgdavid merged 36 commits intostorage-config-uifrom
dgdavid merged 36 commits intostorage-config-uifrom
Conversation
As a first step before migrating to PatternFly v6
As part of the migration to PF v6. It also use PF/Content for replacing a deprecated PF/Chip.
Use Start and End suffix instead of Left and Right.
No longer used in PF v6.
For using right values for PF v6.
No longer needed in PF v6.
No longer available in PF v6.
As part of the PF v6 migration.
For using PF/Masthead as recommended in PF v6.
As recommended by PF v6.
For accepting the description prop sometimes needed for the header.
To properly look for the menu actions at the document body instead of the row where the toggler lives. This change is needed because in PFv6 "The default value of appendTo on Dropdown, Select, and Popper has been updated to `document.body`" Maybe in the future the appendTo prop is added to the actions menu instead.
Which was wrongly using getByText instead of getByRole for working with buttons.
Switch instead checkbox
Most probably it will be drop in the short term.
Renders an emtpy Masthead instead of nothing when there is not header at all. This is needed in order to have the document structure expected by PatternFly CSS to make things works as expected (i.e., allowing the content fill the space reserved for the sidebar).
Intead of the custom core/Center one, which is going to be deleted.
Same than done at 9eaaa81, but for files not previously adapted.
imobachgs
approved these changes
Jan 16, 2025
dgdavid
added a commit
that referenced
this pull request
Jan 20, 2025
A continuation of #1900 for basically introducing some bits of brand.suse.com just for an initial test and feedback from developers putting their hands on the storage-config-ui branch. For the full list of changes, please see commit by commit. Please, merge it ASAP in the feature branch to minimize merge conflicts.
dgdavid
added a commit
that referenced
this pull request
Jan 29, 2025
A continuation of #1900 and #1921. To know more about introduced changes, please see commit by commit, but it basically still polishing visual aspects after the migration to PF6 The idea of this PR is to minimize the risk of big merge conflicts by introducing adjustments done until now in the feature branch ASAP. But still not being the last migration round.
dgdavid
added a commit
that referenced
this pull request
Feb 3, 2025
dgdavid
added a commit
to joseivanlopez/agama
that referenced
this pull request
Feb 5, 2025
Lost while deleting all previous CSS during the migration to PF6. I.e., related to - agama-project#1900 - agama-project#1921 - agama-project#1954 - agama-project#1961
dgdavid
added a commit
to joseivanlopez/agama
that referenced
this pull request
Feb 6, 2025
Lost while deleting all previous CSS during the migration to PF6. I.e., related to - agama-project#1900 - agama-project#1921 - agama-project#1954 - agama-project#1961
Merged
imobachgs
added a commit
that referenced
this pull request
Feb 26, 2025
Prepare for releasing Agama 12: * #1858 * #1887 * #1890 * #1892 * #1893 * #1894 * #1896 * #1898 * #1899 * #1900 * #1901 * #1906 * #1908 * #1909 * #1910 * #1911 * #1912 * #1914 * #1915 * #1917 * #1919 * #1920 * #1921 * #1922 * #1923 * #1924 * #1926 * #1927 * #1928 * #1929 * #1930 * #1931 * #1932 * #1933 * #1934 * #1935 * #1936 * #1937 * #1938 * #1939 * #1942 * #1943 * #1945 * #1948 * #1949 * #1952 * #1953 * #1954 * #1955 * #1957 * #1958 * #1959 * #1961 * #1963 * #1964 * #1967 * #1969 * #1970 * #1971 * #1972 * #1973 * #1974 * #1975 * #1976 * #1977 * #1979 * #1980 * #1981 * #1982 * #1984 * #1986 * #1987 * #1988 * #1990 * #1991 * #1992 * #1993 * #1995 * #1996 * #1997 * #1999 * #2000 * #2001 * #2002 * #2003 * #2004 * #2005 * #2006 * #2007 * #2008 * #2009 * #2010 * #2011 * #2012 * #2013 * #2014 * #2015 * #2016 * #2017 * #2019 * #2021 * #2022 * #2025 * #2027 * #2029 * #2030 * #2031 * #2033 * #2034 * #2035 * #2036 * #2037 * #2038 * #2039 * #2040 * #2045 * #2046 * #2050 * #2053 * #2054 * #2055 * #2056 * #2058 * #2060 * #2061 * #2062 * #2063 * #2064 * #2066 * #2067 * #2068 * #2069 * #2070 * #2071 * #2072 * #2073 * #2075 * #2076 * #2080 * #2082 * #2083
This file contains hidden or 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
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.
Problem
On October 31th, 2024 PatternFly released it's 6th version, which comes with interesting changes. It's look&feel has changed a lot and it has started to make use of tokens, which can be an opportunity for sanitizing the Agama CSS overrides and to start a good foundation for allowing themes in the Agama web interface. Especially, having in mind that there is a SUSE branding refinement too.
Solution
Start migrating to PatternFly 6.
This first round of changes covers several code adaptations as well as some Agama refinements like the deletion of dead code.
Testing
Notes
This PR is not against a feature branch directly on top of
masterbranch because we have decided to deliver this together the new storage interface.Screenshots
This first round does not take too much care about the final result, which makes useless taking screenshots.