List view
I would like to try and finalize both the configuration API for this plugin as well as the Builder API. I think too many projects stay "pre-1.0" for too long and when we hit the first Alpha release we really need to come close to closing the API surface down. This milestone will offer some changes to the Builder API and will largely close the configuration API which this plugin provides. Notes / Goals: - initially the shape of the configuration API was constrained a bit due to backward compatibility (but Anthony has since forked this simpler approach) - my original goal of the Builder API was to hook into an advanced event pipeline while not changing the core configuration API of this plugin; but today I think if we can maintain most of it but provide useful hooks directly in this API then exposing the Builder API directly to end users may not be needed in many/most cases. - creating the Builder API has allowed me to increase the functional footprint a lot and in the mean time I've also been looking into Rust parsers that might potentially get involved down the road. - the culmination of this learning has led me to believe that the next release should: 1. Both the _configuration API_ and _Builder API_ should be complete outside of critical adjustments that are thought of by the community 2. **Configuration API:** expect all _deprecated_ properties in current configuration API to be removed but for a lot of new ones to be added. This will include the ability to quickly and easily hook into various parts of the transformation lifecycle without needing to be involved in the Builder API. 3. **Builder API:** this will become less and less of a concern to external users but will still be a useful way for anyone who wants to contribute reusable hooks to do so
Overdue by 3 year(s)•Due by September 30, 2022