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

Should be able to update all followed tags with one click #1346

Closed
2lach opened this issue Dec 17, 2018 · 9 comments
Closed

Should be able to update all followed tags with one click #1346

2lach opened this issue Dec 17, 2018 · 9 comments
Milestone

Comments

@2lach
Copy link

2lach commented Dec 17, 2018

Problem/ feature request:
On the Followed tags page the user can only submit a single new value for follow weight per submit.

Current page:
following page current

Proposed solution
Since i suppose most users of dev.to (myself included) update several topics at the same time, I suggest a update all button.
This way there is no need for several clicks when updating follow weights = () => which makes happier users and also less data traffic with fewer requests.

Solution illustrated:
following page proposal

Alternatives
Keep it as is or maybe just save all edited values in localStorage so the input doesn't loose it on Submit.
Not as awesome as with an update all button. but still the follow weight is a nice feature in an already awesome community.

Have an awesome day!

@Zhao-Andy
Copy link
Contributor

Hey @2lach, thanks for the feature request! This definitely can be improved, and I think we'll want to discuss which option is best to resolve the UX here.

@2lach
Copy link
Author

2lach commented Dec 18, 2018

Glad to it @Zhao-Andy 👍

IMHO there are two main ways to go about the UX:

Option 1: Would be to do as in the image above in the feature request -> Solution illustrated which is basically adds a new button and keeps the existing submit buttons.
The new button can be added at the top or bottom of the page. The bottom of the page feels more natural than placing it at the top as in my illustration.

Options 2:
Remove all existing submit buttons and only keep the Update all this would give the user less options but also make the UI clearer and cleaner.

@jessleenyc jessleenyc added the external contributors welcome contribution is welcome! label Dec 18, 2018
@jessleenyc jessleenyc added this to the 2019 Q1 milestone Dec 18, 2018
@Link2Twenty
Copy link
Contributor

While we're looking at this they should be number inputs really.

<input type="number" step="0.1" />

Left field:
Thought I'd throw in a totally random idea, how about importance sliders, 0 to 10, that update on change?

@jessleenyc
Copy link
Contributor

For whoever wants to grab this, I think option 2 makes a lot of sense here.

@jessleenyc jessleenyc changed the title Should be able to updated all followed tags with one click Should be able to update all followed tags with one click Aug 7, 2019
@2lach
Copy link
Author

2lach commented Aug 10, 2019

Hey @jessleenyc, hope all is well!
I totally forgot about this 😋 cool that you brought it up again 👍 I could take some time and fix the UI/UX part.

However, being honest i don't see that i will have the time to get into and fix the backend parts (been a couple of years since i wrote a line of ruby).

So if thats cool i can fix the front-end.

Have a good one 😎

@jessleenyc
Copy link
Contributor

Cool, want to give me a ping when you have something and we'll finish it up?

@xanderyzwich
Copy link

I'd also offer an alternative that maybe have the submit button not require a reload. I understand that this will likely not allow for the element to move into order, but I feel in the bulk update scenario that is acceptable. The biggest headache about this to me is in the page reload and having to scroll back down to where I just was and doing this a few dozen times when editing my weighting scheme.

@2lach
Copy link
Author

2lach commented Mar 10, 2020

If @xanderyzwich feels like you have a suitable solution feel free to take over this issue.

I have not been able to find the time to do this task for some time and most likely will not now either.

@cmgorton
Copy link
Contributor

Looks like this feature request was addressed in PR #11454. Going to go a head and close this issue!

@cmgorton cmgorton removed this from Keep this issue/pr in OSS Rotation: Triage stale issues/pr Feb 19, 2021
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

No branches or pull requests

8 participants