Add some handling for ObjectCustomFieldValues to rt-validator #64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
September 1, 2013 11:00
…tCustomFieldValue that no longer exists and delete the transaction.
…ences an ObjectId (Ticket) that is no longer in the database.
|
Correct direction. Commit messages are too long, use one short line, empty line and description as long as you like, for example "delete OCFV records pointing at not existing object" for 30a401d and describe further in the description. The following command is your friend, allows to change history: git checkout -b tmp |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are no real verifications about ObjectCustomFieldValues dependancies and relations. This aims to improve it a little bit. Ref: http://lists.bestpractical.com/pipermail/rt-users/2013-August/081425.html