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

Render contact fields using labels #110

Merged
merged 6 commits into from
Jul 22, 2016
Merged

Render contact fields using labels #110

merged 6 commits into from
Jul 22, 2016

Conversation

rowanseymour
Copy link
Contributor

@rowanseymour rowanseymour commented Jul 21, 2016

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

screen shot 2016-07-21 at 14 57 05

becomes:

screen shot 2016-07-21 at 15 05 08

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 505467a on field_labels into 607191f on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling cdb72b7 on field_labels into 607191f on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling d56b19c on field_labels into 607191f on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f7c4151 on field_labels into 607191f on master.

#----------------------------------------------------------------------------
# A contact field value
#----------------------------------------------------------------------------
directives.directive('cpFieldvalue', () ->
Copy link
Contributor Author

@rowanseymour rowanseymour Jul 21, 2016

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.

Copy link
Contributor

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.

@rowanseymour rowanseymour merged commit 0562930 into master Jul 22, 2016
@rowanseymour rowanseymour deleted the field_labels branch July 22, 2016 06:39
rowanseymour pushed a commit that referenced this pull request Nov 18, 2016
…w-changes-languages

Feature/openhelpd 100 faq review changes languages
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

Successfully merging this pull request may close these issues.

None yet

3 participants