feat(kit): use lazy loading strategy in avatar component

[vadimk7]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows Conventional Commits
• 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
• Refactoring (no functional changes, no api changes)
• Other... Please describe:

What is the current behavior?

Closes #62

What is the new behavior?

All avatar images are loaded lazily

Does this PR introduce a breaking change?

• Yes
• No

Other information

[MarsiBarsi]

Spasibo, Vadim, for your contribution! :)

[vadimk7]

@waterplea, @MarsiBarsi, thanks for submitting my pr 🙂
About direct import from entrypoint, I thought this kind of import allows to include only used directives in the avatar module and optimize the resulting bundle, isn't it?

[waterplea]

@waterplea, @MarsiBarsi, thanks for submitting my pr 🙂
About direct import from entrypoint, I thought this kind of import allows to include only used directives in the avatar module and optimize the resulting bundle, isn't it?

Yes, but in our library every secondary entry point becomes primary entry point for the higher level imports. This way it is already optimized, no matter how deep you import. So we try to use the highest possible point so if you, say, import another directive — it would be placed in the same import line.