-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
View Switcher - Default Icon Display #6947
Labels
good first issue
Good for newcomers
prio: med
scope: front
Issues that are affecting the frontend side only
size: short
Comments
Bonapara
added
good first issue
Good for newcomers
scope: front
Issues that are affecting the frontend side only
size: short
labels
Sep 9, 2024
working on it @Bonapara |
Thanks @Nabhag8848! |
@Bonapara, I have resolved this bug, could you please assign it to me so that I can raise a PR? |
hey @rathodvinod5 make the PR. thanks :) |
@Nabhag8848, Thanks. |
lucasbordeau
added a commit
that referenced
this issue
Oct 10, 2024
Fixes #6947 (View switcher default icon display) --------- Co-authored-by: Lucas Bordeau <[email protected]>
harshit078
pushed a commit
to harshit078/twenty
that referenced
this issue
Oct 14, 2024
Fixes twentyhq#6947 (View switcher default icon display) --------- Co-authored-by: Lucas Bordeau <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
prio: med
scope: front
Issues that are affecting the frontend side only
size: short
Current behavior
If not customized, The view icon is set to the
Kanban
orTable
icon. But the icon displayed in theIcon Picker
doesn't reflect this. (It displayed the last icon selected in the picker, and by default the list icon)CleanShot.2024-09-09.at.11.47.52.mp4
Desired Behavior
The picker should display the Table icon by default. If the icon hasn't been edited, the picker should reflect the default icon (Table or Kanban) until the user takes control and chooses a custom icon.
The text was updated successfully, but these errors were encountered: