Closed mbland closed 8 years ago
Probably contact.url
and contact.text
I think.
---
contact:
url: https://blah.blah/blah
text: Black blah blah
something like that. That seems more extensible for the future, anyway.
Sounds good to me.
cc: @melodykramer @jeremiak
This is how a fully specified contact field looks on staging:
That is based on the following format:
contact:
- url: mailto:michael.bland@acm.org
text: Mike Bland
- url: https://github.com/18F/hmac-authentication-npm/issues
text: 18F/hmac-authentication-npm issues
Is that the expected format? If so, I'd be happy to submit a fix.
Yep, that's the new contact:
format. A fix is surely welcome, if @gboone or I don't get to it first.
Thanks, @mbland. I'll take a look, then.
Hey @gboone, you'd mentioned being cool with just getting the data for the
contacts:
field from the Team API and posting it straight into the template, rather than parsing it as an email address or as a GitHub URL fragment as we do now. Would you want to have just a raw URL (mailto:
orhttps:
that you'd post as<a href="{{ contact_url }}">{{ contact_url }}</a>
, or have an object withurl:
andtext:
fields that you'd render as<a href="{{ contact.url }}">{{ contact.text }}</>
?cc: @monfresh re: 18F/github-dashing#24