This is probably not the preferred location for this, but this is an easy and vital enhancement request for the next version, or the even next minor release.
Using the Vault command-line client to fetch HISTORY, we're getting-back invalid XML, and hence won't load in a DOM, when a developer uses nested quotes in a checkin comment.
History can return a ton of XML. In our case, nearly 20,000 lines (and counting). The command-line client is slow to begin with, and additionally we need to post-process this mountain of XML in a custom line-parser before it's usable.
For the record, here's the test case that currently fails. I hope this fragment from our XML will display for you. In this case, there are nested quotes in the comment.
< snip >
< item ... comment="1.02 added "select the repair option in the "program maintenance" dialog..." and screenshot to section 4.3." ... />
< /snip >
You want to encode all quotes, not just the outer pair within the comment text.
It's a bit silly, and arbitrary, that Vault comments aren't editable.
**--** Steve
Next Version: Enhancement Request -- XML comment cleansing
Moderator: SourceGear
-
- Posts: 13
- Joined: Sat Apr 05, 2008 7:20 pm
- Location: Canada
Re: Next Version: Enhancement Request -- XML comment cleansing
Comments are editable. Log in to the GUI client as the admin user, or the user who committed the transaction. The Edit Comment button on the Transaction Details dialog will enable.
Subscribe to the Fortress/Vault blog
-
- Posts: 13
- Joined: Sat Apr 05, 2008 7:20 pm
- Location: Canada
Re: Next Version: Enhancement Request -- XML comment cleansing
Thanks Jeremy. Er, do you have a tracking number for this dishing dirty XML bug?
**--** Steve
**--** Steve
Re: Next Version: Enhancement Request -- XML comment cleansing
This has been logged as bug 13714. Thanks for the report.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Re: Next Version: Enhancement Request -- XML comment cleansing
Can we get an update for this bug? We are also experiencing the same problem with double quotes (") inside a comment.
Here are the versions we are running.
[1/28/2009 2:37:55 PM] Version Check: This Vault client is version 4.1.2.18185
[1/28/2009 2:37:55 PM] Version Check: Your Vault server is version 4.1.2.18185
[1/28/2009 2:37:56 PM] Version Check: The following information was retrieved from the SourceGear website. No information was sent to SourceGear. You can disable this part of the version check from the Options dialog.
[1/28/2009 2:37:56 PM] Version Check: The most recent Vault release is version 4.1.4.18402
Thanks!
Jeff
Here are the versions we are running.
[1/28/2009 2:37:55 PM] Version Check: This Vault client is version 4.1.2.18185
[1/28/2009 2:37:55 PM] Version Check: Your Vault server is version 4.1.2.18185
[1/28/2009 2:37:56 PM] Version Check: The following information was retrieved from the SourceGear website. No information was sent to SourceGear. You can disable this part of the version check from the Options dialog.
[1/28/2009 2:37:56 PM] Version Check: The most recent Vault release is version 4.1.4.18402
Thanks!
Jeff
Re: Next Version: Enhancement Request -- XML comment cleansing
This is scheduled to be fixed in Vault 5.0, which is currently under development. I don't have a target date as yet, but it will be later this year.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager