I think I was the original person to suggest using RegEx, although perhaps
the idea has "morphed" into other areas.
When I suggested it, the RegEx would have been used to validate the issue
ID. As such, it would really just need to be run on the text typed into
that field, not the entire log message. I think this would have just been
for simple validations, similar to what we already provide to say if an
issue ID is numeric. In my system, as an example, the Bug ID string would
always have to be 8 or 10 total characters, so I might provide an
expression to validate that. Some people use systems with complicated
ID's like ABCD/123 that could also have a simple validation performed.
You pretty much convinced me that this isn't really needed.
So to come back to your question, I don't understand what you would be
using expressions for? Is it just to identify the bug ID's in a log
message so that you know what to turn into hyperlinks? Does that really
need that much improving? Are you thinking of some new UI such as showing
the Bug ID's separate from the log message and this is how you would
extract them?
Thanks
Mark
SteveKing <steveking@gmx.ch> wrote on 02/11/2005 12:23:04 PM:
> Hi guys,
>
> I'm currently working on the specs to enhance the integration of TSVN
> with issuetrackers by using regex. And I've come to a point where I need
> your help and feedback.
>
> With regex it's possible to extract a bug ID from a log message and use
> that to link a commit to a specific issue. The question is now if _one_
> reges is enough or if we need two of them.
>
> One regex:
> using lookahead/lookbehind it's possible to just extract the bug ID
> alone but still have enforced an e.g. "Issue #" in front of the bare bug
> ID. But most of the available regex libs don't support repetition or
> optional items in lookahead/lookbehind expressions. So AFAIK a regex
> which can extract the bare bug ID's from a string like
> Issue #573, #928
> and
> Issues #872, #098
> isn't possible because of the optional 's' in the lookbehind.
>
> Two regex:
> the first regex would match the whole string, e.g.
> Issue #487, #938
> or
> Issues #872, #098
> and the second regex would then extract the bare bug ID's from the
> string matched by the first regex.
>
> And keep in mind that the simpler regex libs don't even support
> lookahead/lookbehind at all (like javascript and ruby).
>
> So what do you think is the way we should go?
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Feb 11 18:54:17 2005