You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal fields in the PDC are actually arrays of strings. This allows things like board_of_directors: ['Jane Doe', 'John Smith'].
None of our templates actually respect this, however. We just write them to screen as if they were strings, e.g. <span>{value}</span>. As far as we know, no fields actually contain more than one value at the moment. But if value in that example were an array like ['foo', 'bar'] then it would display as <span>foobar</span>.
We need to decide how we display or delimit arrays of data. Is there a universal answer that supports all our field types, or will we need different solutions for, say, budgets than mission statements?
The text was updated successfully, but these errors were encountered:
Join with a text delimiter. This is simple and can happen outside of the React/JSX context, such as in a utility method. However, whatever delimiter we choose will probably appear in real content, so it won't be clear whether we are looking at multiple values joined, or a single value that contains that delimiter.
Compose a bulleted list. Simple and clear, but will have to happen in React/JSX rather than a simple utility method. Still possibly the best answer.
Proposal fields in the PDC are actually arrays of strings. This allows things like
board_of_directors: ['Jane Doe', 'John Smith']
.None of our templates actually respect this, however. We just write them to screen as if they were strings, e.g.
<span>{value}</span>
. As far as we know, no fields actually contain more than one value at the moment. But ifvalue
in that example were an array like['foo', 'bar']
then it would display as<span>foobar</span>
.We need to decide how we display or delimit arrays of data. Is there a universal answer that supports all our field types, or will we need different solutions for, say, budgets than mission statements?
The text was updated successfully, but these errors were encountered: