Custom Fields: Add slugs closes #195 #205
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
question
S
UX research
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: local-it/mitgliederverwaltung#205
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/custom-field-slug"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of the implemented changes
The changes were:
Definition of Done
Code Quality
Accessibility
Testing
Overall great work !! 💯
Just the question about showing the slug to the user, I think it might be more confusing for them.
@ -51,0 +54,4 @@<%!-- Show slug in edit mode (read-only) --%><div :if={@custom_field} class="mb-4"><label class="block text-sm font-semibold leading-6 text-zinc-800">I asked myself if we should hide that information from the user as it is rather a technical info?
@ -44,3 +45,3 @@row_click={fn {_id, custom_field} -> JS.navigate(~p"/custom_fields/#{custom_field}") end}><:col :let={{_id, custom_field}} label="Id">{custom_field.id}</:col><:col :let={{_id, custom_field}} label="Slug">{custom_field.slug}</:col>Same as above
@ -48,6 +50,8 @@ defmodule MvWeb.CustomFieldLive.Show do<.list><:item title="Id">{@custom_field.id}</:item><:item title="Slug">{@custom_field.slug}</:item>And here :)
It's the bridge between technical details and admin information. It will be used for debugging, import/export and other purposes, where the id is not practical. Therefore I think there should be places where the admin can inspect the slug.
038299140btoefb3e1cc37