Feature/detect template break changes

[rsaz]

Pull Request Guidelines

Our guidelines for submitting a pull request.

Before submitting your PR, please verify the following:

• The commit message follows our guidelines:

  Make sure you prefix your commit message with the type of change you are making. Your commit message should look like this: type: description of the change.

  • Fixing a bug : fix: description of the change.
  • Adding a new feature : feat: description of the change.

See the options for the different types of changes you can make in the package.json file of your project.

Leave the options below unchecked if they are not applicable to your Pull Request.

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Test
• Other... Please describe:

Does this PR introduce a breaking change?

• Yes
• No

If yes Please describe the impact and mitigation strategy for existing applications.

What was changed?

Please describe what you have changed in this PR.

Other information

Any other information that is important to this PR.

[juliano-soares]

Good job!