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

Implement a Settings Content component #1221

Merged
merged 11 commits into from Nov 26, 2022

Conversation

jmt-gh
Copy link
Contributor

@jmt-gh jmt-gh commented Nov 26, 2022

In previous commits, we consolidated all of the settings pages to have the same styling. This commit takes that one step further by extracting out all of that logic to a singular component. This component wraps the content of the settings pages themselves, so it is very easy to use. As well, it has the functionality to pass through the header text, description text, and a method that could be needed to "add a new one" of something for the page (users, libraries, etc.).

This commit adds a new settings conent component. This is a container
component for the settings pages, so that they all get the same
formatting by default. It handles the header text, description text, and
any "add new" plus button as needed.
This commit moves the library settings page over to use the new
component. This page is 1 of 2 that actually has a component for itself,
so it was mostly just modifying that existing component and wrapping it
This commit moves the Users settings page to use the new Settings
Content component. Similar to the Libraries page, this one is already a
component. I mimiced the behavior of the existing libraries component to
get the same functionality needed here
This commit moves the Backup page to use the new settings component.

As part of this, I had to do a little bit of modification for some of
the strings, as I cleaned up the way the strings are laid out on the
page.
@advplyr
Copy link
Owner

advplyr commented Nov 26, 2022

Makes sense, thanks!

@advplyr advplyr merged commit 7b0b79e into advplyr:master Nov 26, 2022
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.

None yet

2 participants