fix: updating tp content from empty to value doesn't create the tp instance

[MichalK6677]

fix: updating tp content from empty to value doesn't create the tp instance)

Fixes #138

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: CONTRIBUTING.md#commit
• 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?

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

What is the current behavior?

#138

What is the new behavior?

The solution here is to create/destroy the instance depending on the content changes as well and not just on initialization.

Does this PR introduce a breaking change?

[ ] Yes
[x ] No

Other information

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[shaharkazaz]

Left a couple of comments, please add specs for this case as well 👍

[shaharkazaz]

There is a situation where we might subscribe several times to the events.
Let's say I'm starting with no content, then adding content. I'm subscribed twice no?
I think the creation trigger should be uncoupled from the instance existence. If we already decided to create an instance, we should always create it here and not resubscribe to the events.