Default implementation of handleInvalidEmptyPreconditionCase added in AbtractFormattedChangeLogParser to avoid breaking extensions

[MalloD12]

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

Recently with the merge of this PR the team has noticed this is breaking extensions, so just move the code implementation of handleInvalidEmptyPreconditionCase to the abstract class which should fix this issue if no extension overrides this method.

Things to be aware of

Things to worry about

Additional Context

[vitaliimak]

Thanks, @MalloD12 for such a quick fix!
It should work, but, I'm wondering if it is possible to leave the abstract class without SQL-specific implementation. The commercial MongoDB extension does not use sql-check, table-exists, and so on.
Is it possible to write something like this?

protected void handleInvalidEmptyPreconditionCase(ChangeLogParameters changeLogParameters, ChangeSet changeSet, Matcher preconditionMatcher) throws ChangeLogParseException {
    throw new NotImplementedException();
}

And left SQL-specific code in the FormattedSqlChangeLogParser class.

[MalloD12]

protected void handleInvalidEmptyPreconditionCase(ChangeLogParameters changeLogParameters, ChangeSet changeSet, Matcher preconditionMatcher) throws ChangeLogParseException {
throw new NotImplementedException();
}

Ohh, I see. I get it now. Sure, I can do that @vitaliimak.