Crash, if DataSubjectId with PersonalData is used but no cryptoshredding is explicitly enabled/disabled

[DanielBadura]

Right now, users could add the attributes but not enabling the option in the config: this leads to no impact of the attributes without any notice for the user. My suggestion would be to throw an explaining exception if there is any event which is using these attributes but the config is not enabled or explicitly set to be disabled. The exception should lead the user to configure the crypto option.

[DavidBadura]

I find that too complex. You'd have to check all event/aggregate metadata to see if any information has been set regarding it.

Symfony doesn't do that either if you use attributes that you haven't enabled as a feature. It's the other way around: you've enabled a feature but forgotten to set the necessary attributes.

I'm against implementing such checks.

[DanielBadura]

Another idea: for v4 enable crypto shredding by default?