I propose splitting the data_privacy crate into two separate crates: one intended for libraries and another for applications.
The library-focused crate would expose a minimal, stable set of functionality for data classification only, while the application-focused crate would define redactors and other application-specific helpers.
The primary goal is to stabilize the library-facing API and reduce the possibility of future breaking changes. I've already encountered issues when classified types defined using 0.10 version were incompatible with redactors from 0.11 version of data_pravicy crate.
@ralfbiedert , @geeknoid
I propose splitting the data_privacy crate into two separate crates: one intended for libraries and another for applications.
The library-focused crate would expose a minimal, stable set of functionality for data classification only, while the application-focused crate would define redactors and other application-specific helpers.
The primary goal is to stabilize the library-facing API and reduce the possibility of future breaking changes. I've already encountered issues when classified types defined using 0.10 version were incompatible with redactors from 0.11 version of data_pravicy crate.
@ralfbiedert , @geeknoid