Hey guys, I was recently testing a PR and was seeing inconsistent FileNotFound exceptions using a path specified in a processor property. It ended up being because one of the flows had a trailing space in the value and the other didn't.
I'm curious about whether there's any thoughts on what the convention should be here? I.e., should the processor trim the property value when pulling it out of the context? This is a trivial matter in some sense, but (ignoring whether it's good) it is possible to create filesystem objects with trailing spaces, so it could be the data flow developer's real intention. On the other hand, it's a bad user experience. Having to just remember to trim the property kinda sucks too because then every processor implementation will need to do it and that'll probably be inconsistent. I started thinking maybe it'd be worth adding an asPath() to StandardPropertyValue which could enforce an opinion on this. Thoughts? -joey
