Open jduss4 opened 6 years ago
I can't ever think of a situation we'd want a newline in a keyword, so I like option 1
Option 1 seems like a reasonable approach to me too. The ability to override later if it ever becomes necessary should cover our needs :)
Agreed! Let's plan on doing this next time datura comes up. I do not believe any of the existing repos using datura in production or pseudo production (cather, whitman) will need overrides if return characters are removed
I cannot think of any situations where keywords should have return characters in them, since we are using them as exact matches / faceting.
Related to issues in API: https://github.com/CDRH/api/pull/82 https://github.com/CDRH/api/pull/81
We have two options I see: We could make this change across all keyword fields automatically and then if some project does need a newline in a keyword field, we can cross that bridge later with an override, etc. Alternatively, we could add a line to each keyword field that smushes the contents, but then any overrides of those methods would need to imitate the behavior, as well.