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

feat(frontend/settings): organize overlay buttons next to each other #616

Merged
merged 5 commits into from
Oct 29, 2020
Merged

feat(frontend/settings): organize overlay buttons next to each other #616

merged 5 commits into from
Oct 29, 2020

Conversation

bhajneet
Copy link
Member

Summary of PR

Organizes buttons in settings/overlay a bit better

image

Tests for unexpected behavior

  • none_whatsoever

Time spent on PR

  • actual solution took less than an hour
  • suffering took multiple hours (to try and work within a stale branch)

Linked issues

Fix #

Reviewers

@Harjot1Singh

ideally there would be a single button component for the entire settings page since there are now multiple ways to show a button, but have used grid items for spacing
it makes sense that a user would customize something on the theme tool then look for the folder where they must put the generated file

similarly it makes sense for users who do not wish to customize and simply want to drop in an organization's theme file and then select it to have the overlay folder button higher up
@bhajneet bhajneet added Effort 1 Simple task (code/non-code). Impacts Few Does not affect many end-users. Scope: Frontend/Settings Status: Merge □ Type Story Feature or requirement written from the user's perspective using non-technical language. labels Oct 29, 2020
@bhajneet bhajneet changed the title Bhajneet/issue586 feat(frontend/settings): organize overlay buttons next to each other Oct 29, 2020
@Harjot1Singh Harjot1Singh merged commit 71f6622 into shabados:dev Oct 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Effort 1 Simple task (code/non-code). Impacts Few Does not affect many end-users. Scope: Frontend/Settings □ Type Story Feature or requirement written from the user's perspective using non-technical language.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants