Sergei Sevriugin

@marco-prontera Thanks Marco, I will take a look

Hello, @adafee15, thanks for rising the issue. I have tried to check with the lates version of the GVL https://vendor-list.consensu.org/v3/vendor-list.json running the following code snippet in `ts-node`. No issue found....

@adafee15 could you please test my code snippet with lates GVL v24 and send me error message that you are getting, thanks ```typescrypt import gvlJson from './data/vendor-list.json'; import { GVL,...

ok, makes sense, I agree, we need to improve the vendor model

We have implemented [this](https://github.com/didomi/iabtcf-es-archived/pull/4) maybe we can reuse some ideas here

We have testes this one https://github.com/didomi/iabtcf-es-archived/pull/4 for more then one year so it will be save to apply and no action needed from library users to use this feature, imo,...

@HeinzBaumann Could we have a link here to the lates approved GVL format, thanks

@HeinzBaumann Should we support the legacy version of the GVL in the library and make new fields optional? ```typescript export interface Declarations { purposes: IntMap; specialPurposes: IntMap; features: IntMap; specialFeatures:...

Thanks for comments. I will try to create a PR making these fields optional for now and will add TODO comment to change them to mandatory when the transition period...

`tcString` is actually GDPR string maybe missing some custom vendors and purposes that CMPs can add to additional consent stored it in separate cookies and provide it in result of...