Review classes and isolate non-API in impl packages
Basics
Logistics
Basics
Logistics
Description
As a step towards proper modularisation in a future release, we should isolate any classes we deem to be non-API.
Most classes are either delivering direct user-visible functionality, or allowing such functionality to be built by others, so there aren't going to be a lot of these. Something like XMLSignatureValidator would definitely count though.
Environment
None
Activity
Ian YoungFebruary 1, 2023 at 2:13 PM
Reviewed the rest of the codebase and this looks like everything for now.
Ian YoungJanuary 31, 2023 at 8:58 AM
PipelineCallable and FutureSupport seem like implementation details.
As a step towards proper modularisation in a future release, we should isolate any classes we deem to be non-API.
Most classes are either delivering direct user-visible functionality, or allowing such functionality to be built by others, so there aren't going to be a lot of these. Something like
XMLSignatureValidatorwould definitely count though.