[FOLIO-2653] Remove leading and trailing whitespace from text properties Created: 22/Jun/20 Updated: 03/Feb/21 Resolved: 03/Feb/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Marc Johnson | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | potential-decision | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
Decision Should FOLIO API's automatically remove leading or trailing whitespace from text properties? Context Split from
|
| Comments |
| Comment by Marc Johnson [ 22/Jun/20 ] |
|
I'm moving the general conversation about this here from [UII-1528].
I am biased against changes to data being made automatically. It relies on inferring the intent of a client, which can often be a fools errand. It also increases the coupling between client and the server because the client needs to know this is being done automatically (e.g. in case it wanted to compare representations) and may come to believe it can rely on the server to always do this. I think these kinds of automatic changes tend to be well intended and yet cause surprises. In some cases, I think those become challenging situations to address, as systems then need exceptions to these rules, which increases complexity.
Sure, I'm more than willing to consider it and accept it being corrected automatically. I tend to want to throw some caution into the mix about decisions like this. One of the early challenges that we might encounter could be how to classify the properties.
It probably isn't controversial. |
| Comment by Marc Johnson [ 03/Feb/21 ] |
|
Closing as pre-dates the new decision making process and has not progressed |