Skip to content

Conversation

wwillard7800
Copy link
Contributor

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)
  • Enhancement/New feature (adds functionality without impacting existing logic)
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Things to be aware of

Things to worry about

Additional Context

Improve regex for endDelimiter and rollbackEndDelimiter
@filipelautert filipelautert self-assigned this May 3, 2024
@filipelautert
Copy link
Collaborator

@jasonlyle88 once your setup is fixed could you confirm that this one fixes your issue?

@jasonlyle88
Copy link
Contributor

@filipelautert Yup, that fix does it!
@wwillard7800 Thanks for the quick fix!

Only question I have is if we want to add the word boundary check to the rest of the attribute REGEX variables? I think there are 22 more of them (i.e. runOnChange, runAlways, etc). There aren't any other substring issues that I saw from a quick scan... but more as a future safe guard.

Thoughts?

@wwillard7800
Copy link
Contributor Author

That would be good defensive programming. It may be worth a tech debt ticket.

@rberezen
Copy link
Contributor

@filipelautert @wwillard7800 we need to merge fix for the pro-test with this pr
https://github.com/liquibase/liquibase-pro-tests/pull/1444

@filipelautert filipelautert merged commit 6d322fe into master Jun 10, 2024
@filipelautert filipelautert deleted the fix-rollback-end-delimiter-parsing branch June 10, 2024 16:04
@filipelautert filipelautert added this to the 1NEXT milestone Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

SQL formatted changelogs mistakenly identify rollbackEndDelimiter value for endDelimiter value
4 participants