Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Remove old user and room settings #2554

Merged
merged 4 commits into from
Feb 6, 2019
Merged

Conversation

turt2live
Copy link
Member

@turt2live turt2live commented Feb 1, 2019

Part of element-hq/element-web#8207
This might be a change which we want to land after FOSDEM. We decided to do this, and here we are.

This takes out the old user and room settings, replacing the paths with the new dialog editions. The labs setting has been removed in order to support this change.

In addition to removing the old components outright, some older components which were only used by the settings pages have been removed. The exception is the ColorSettings component as it has a high chance of sticking around in the future.

Styles that were shared by the settings components have been broken out to dedicated sections, making it easier to remove the old styles entirely.

Some stability testing of the app has been performed to ensure the app still works, however given the scope of this change there is a possibility of some broken functionality.

@turt2live turt2live requested review from a team and removed request for a team February 1, 2019 06:12
@turt2live
Copy link
Member Author

conclusion: this PR is probably not going to land as-is before FOSDEM. Instead, we're going to enable the new settings for people and take off the temporary tab, leaving removal of the old settings for later.

@turt2live turt2live self-assigned this Feb 1, 2019
@turt2live turt2live force-pushed the travis/settings/delete-the-old branch from f562799 to 397e36e Compare February 4, 2019 20:27
@turt2live turt2live removed the blocked label Feb 4, 2019
This takes out the old user and room settings, replacing the paths with the new dialog editions. The labs setting has been removed in order to support this change.

In addition to removing the old components outright, some older components which were only used by the settings pages have been removed. The exception is the ColorSettings component as it has a high chance of sticking around in the future.

Styles that were shared by the settings components have been broken out to dedicated sections, making it easier to remove the old styles entirely.

Some stability testing of the app has been performed to ensure the app still works, however given the scope of this change there is a possibility of some broken functionality.
@turt2live turt2live force-pushed the travis/settings/delete-the-old branch from 397e36e to eac50aa Compare February 4, 2019 20:40
@turt2live turt2live removed the notready label Feb 4, 2019
@turt2live turt2live requested a review from a team February 4, 2019 20:40
@turt2live turt2live removed their assignment Feb 4, 2019
@jryans jryans self-assigned this Feb 5, 2019
Copy link
Collaborator

@jryans jryans left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall! 😁 I added a few questions, but I don't think another round of review is needed.

@@ -0,0 +1,19 @@
/*
Copyright 2019 New Vector Ltd.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ultra nit: It's currently more common to write Ltd without a full stop in these headers

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in all the legal documents it's with a full stop, so I'm tempted to say we've been doing it wrong elsewhere.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haha, perhaps so... My OCD just hopes we'll choose one way or the other... 😰

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if we just make it 50/50 exactly? Then you get the best of both worlds and a pleasing number.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😅😅😅

/*
* TODO: Make things use this. This is all WIP - see UserSettings.js for usage.
*/
// TODO: Decommission.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be nice to file an issue and link it here for this future work.

@@ -77,7 +77,7 @@ export default React.createClass({
<div role="alert">{ this.state.authError.message || this.state.authError.toString() }</div>
<br />
<AccessibleButton onClick={this._onDismissClick}
className="mx_UserSettings_button"
className="mx_GeneralButton"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is a GeneralButton? Could it just be mx_Button?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A GeneralButton is a button that was using the user settings classes and I didn't want to break anything, so included the extra styles. I haven't tested, but I have a burning feeling that trying to make it a Button will be more effort than it's worth for this PR.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, fair enough. Maybe make a future issue to clean up / simplify button classes?

@turt2live turt2live merged commit 8b5e4a4 into develop Feb 6, 2019
@turt2live
Copy link
Member Author

I've created a bunch of issues for the concerns btw. See 04f2375

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants