Validate formatted SQL changelog for invalid patterns DAT-7721 #2761
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
StevenMassaro
approved these changes
Apr 14, 2022
Comment on lines
122
to
127
| private static final String INVALID_CHANGELOG_INVALID_PRECONDITION_PATTERN = | ||
| "--liquibase formatted sql\n" + | ||
| "\n" + | ||
| "--changeset bboisvert:invalid_precondition\n" + | ||
| "--precondition-invalid-type 123\n" + | ||
| "select 1;" |
There was a problem hiding this comment.
This looks identical to INVALID_CHANGELOG_INVALID_PRECONDITION. Do we need both?
DAT-7721
|
Thank you for reading the fine print. It was supposed to be different, but
I had a copy-and-paste error. It failed as expected, but for the wrong
reason. I have pushed a fix.
…On Thu, Apr 14, 2022 at 3:24 PM Steven Massaro ***@***.***> wrote:
***@***.**** approved this pull request.
------------------------------
In
liquibase-core/src/test/groovy/liquibase/parser/core/formattedsql/FormattedSqlChangeLogParserTest.groovy
<#2761 (comment)>:
> + private static final String INVALID_CHANGELOG_INVALID_PRECONDITION_PATTERN =
+ "--liquibase formatted sql\n" +
+ "\n" +
+ "--changeset bboisvert:invalid_precondition\n" +
+ "--precondition-invalid-type 123\n" +
+ "select 1;"
This looks identical to INVALID_CHANGELOG_INVALID_PRECONDITION. Do we need
both?
—
Reply to this email directly, view it on GitHub
<#2761 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHAEDEXK5LAX5NXPQA6273VFB5JDANCNFSM5TOZF7AQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
suryaaki2
approved these changes
Apr 14, 2022
DAT-7721
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.
Environment
Liquibase Version:
Liquibase Integration & Version: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.>
Liquibase Extension(s) & Version:
Database Vendor & Version:
Operating System Type & Version:
Pull Request Type
Description
A clear and concise description of the issue being addressed. Additional guidance here.
Steps To Reproduce
List the steps to reproduce the behavior.
Actual Behavior
A clear and concise description of what happens in the software before this pull request.
Expected/Desired Behavior
A clear and concise description of what happens in the software after this pull request.
Screenshots (if appropriate)
If applicable, add screenshots to help explain your problem.
Additional Context
Add any other context about the problem here.
Fast Track PR Acceptance Checklist:
Need Help?
Come chat with us in the Liquibase Forum.