[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

Trimming values, fieldnames and tiddler titles makes sense, there may however be a rare occasion where this is needed, however I think the hack would be to use a special space character (that is not trimmed) if you really needed. Of course when possible allow the default to be overridden if

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

Posted here , thanks everyone. On Thursday, August 19, 2021 at 2:08:23 AM UTC-5 PMario wrote: > On Thursday, August 19, 2021 at 12:33:29 AM UTC+2 Soren Bjornstad wrote: > > If I'm misunderstanding, please correct me (and can you link the >>

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

On Thursday, August 19, 2021 at 12:33:29 AM UTC+2 Soren Bjornstad wrote: If I'm misunderstanding, please correct me (and can you link the > discussions on GitHub?). > Sorry, I was talking about field values. You are right, we should trim field names. There is some time left to do so. But

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

I am in favor of stripping out leading and trailing whitespace in field Names during field creation and tiddler import. Best, Joshua F On Wednesday, August 18, 2021 at 1:38:29 PM UTC-7 Soren Bjornstad wrote: > I'll preface this by saying this probably belongs in a GitHub issue, and > I'll be

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

On Wednesday, August 18, 2021 at 1:57:26 PM UTC-7 PMario wrote: > There has been a discussion recently, where a user needed to be able to > add whitespace as needed. And the description of the usecase made sense. > That discussion was related to having leading whitespace in a field *value*,

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

Mario, I don't think the thread you linked is relevant. I'm talking about field *names*, not field values. And I don't see how it would break backwards compatibility with 5.1.x, because 5.1.x didn't allow *any* spaces in field names. If I'm misunderstanding, please correct me (and can you

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

On Wednesday, August 18, 2021 at 10:38:29 PM UTC+2 Soren Bjornstad wrote: > I'll preface this by saying this probably belongs in a GitHub issue, and > I'll be happy to create one over there if we want one. But wanted to get > people's thoughts first, and ASAP because now is our last chance to

[tw5] Re: Should we prohibit leading and trailing whitespace in field names in 5.2.0?

Just realized some people might not be familiar with the term "leading and trailing whitespace"...I mean whitespace at the very beginning or end of the name. In the current prerelease, these are valid and distinct field names (with the quotes removed): "my field" " my field" "my field " "