-
Notifications
You must be signed in to change notification settings - Fork 31
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
Render contact fields using labels #110
Conversation
…ling of pods with actions
#---------------------------------------------------------------------------- | ||
# A contact field value | ||
#---------------------------------------------------------------------------- | ||
directives.directive('cpFieldvalue', () -> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@justinvdm have added this to do formatting of date and numerical values, as we're currently just dumping ISO8601 timestamps on unfortunate users. Logic below should probably be shared in some way with pod values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, noted. I think the plan for the base pod's UI is to expect all item values to be strings. If we start defining custom pods with values of other types, this will come in quite useful though.
…w-changes-languages Feature/openhelpd 100 faq review changes languages
Also updates the styling of the contact details panel on the case page, to use same styling as that which will be used for pods provided by case plugins.
And ensures that date and numerical field values are formatted accordingly. So
becomes: