Let me start directly from the painful points in the current situation with
@vereign/light-utilsis heavy and 95% of it’s functionality used by
iframeneeds to use shared code of public API errors (
StatusAPIError). That’s the reason of having them sticked in a single repo.
- There’s certainly confusion between
@vereign/vframeduring the discussions.
- If a third-party integrator wants to read seals from emails and load iframes, he/she needs to install both
@vereign/vframewhich is really inconvenient.
So, after some thinking I came up with the idea of aggregating existing functionality into a lightweight integration library called
@vereign/lib-seal which is going to expose:
IframeService- to load iframe APIs
SealService- to extract seals from MIME
- List of public API errors
With this optimization, Integrators (Chrome Extension and Outlook Add-in) will be able to sufficiently cover the verification routine at their side using only a single library. And pretty much the same goes for the
@vereign/vframe- gets removed
@vereign/light-utils- preferably it should be used only by Web Verification App and Iframe. Chrome Extension and Outlook Add-In will be able to work without it.
Outlook Add-in. Using the whole API of the library.
iframe- uses Public API errors only
@vereign/mime-normalizer- needs only