[MAGNOLIA-6169] Cleanup whitespace in yaml config files Created: 15/Apr/15 Updated: 08/May/15 Resolved: 15/Apr/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | configuration |
| Affects Version/s: | None |
| Fix Version/s: | 5.4 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Description |
|
In particular when copy-pasting from some sources, non-breaking space and other whitespace characters can be accidentally included in yaml files. Those are not desirable, and not necessarily easy to fix for all users. We could filter them when loading the files. (since our use-case is 99.99% configuration, we can safely assume nobody actually wants non-breaking space in their files - which would be a different story if, say, we stored content in yaml) |
| Comments |
| Comment by Magnolia International [ 15/Apr/15 ] |
|
Done on branch feature/ |