Patch 1 separator6/9/2023 ![]() Do we already have an agreement on this? More comments welcome, especially regarding display and normalization of stored values. In the same move we could (should?) resort to reformatting according to current delimiter settings just for display.Īt least this is my understanding of your proposal. This single port passive Power over Ethernet (POE) injectors provide power to your device from up to 328 ft (100 meters) away. As I see it, this is not the end of the comma as a delimiter in general, just for storage. I'm all for accepting every string and trying to pull out valid tag(s) with best available logic. It isn't easy this, but we should try to not confuse things even further. My meaning was more that the we should accept common patterns and not settle on a single character. I mean, for date/time fields it's natural, to parse and accept only valid entries, why not for keywords/tags too? Nevertheless, we should reach for better standards in this respect. In fact KeywordSuggestPlugin already did some sanitization in the past, and this is another thing I like about it very much. ![]() ![]() However, I do see your point and it would help if there was some normalization for storage (which of course none of the fields do today). For tickets there's no hope to change this, before multiple values per field (see t:#918) get implemented in general, right? Maybe some split and merge logic is not perfect yet, but TagsPlugin itself can store multiple tags per resource in tags Trac db table, so there is no such limitation for tags in general. Well, SQL on multi-value fields is always going to be a pain no matter what.
0 Comments
Leave a Reply. |