Feature/lazy

[lbebber]

What is the purpose of this pull request?

Loads content lazily

https://lazytelemarketing--storecomponents.myvtex.com/

What problem is this solving?

How should this be manually tested?

Screenshots or example usage

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Requires change to documentation, which has been updated accordingly.

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch

• Minor

• Major

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

[lbebber]

This change is just moving code from the root of the react dir to the components dir

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 2.9.8 → 2.10.0

After the publishing process has been completed (check #vtex-io-notifications) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.telemarketing@2.10.0

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖