That sounds good to me. What's the right way for us to "deprecate" the
config subsystem. I guess the simplest thing would be add an @deprecated
decorator to the relevant classes that get generated with a pointer to the
docs on how to migrate.
--Colin
On Tue, Nov 15, 2016 at 5:07 PM, FREEMAN,
You mean the Provider? Most people adapt the Provider and put it in src/
anyway; I would guess this wouldn't really raise much awareness but that
is my own $0.02. The easiest path forward is probably to make sweeping
announcements via email and strong suggestions in the release notes... but
I
Just my 2 cents: I think Option 2 sounds very reasonable.
In SFC, I think we would even be ready to completely adapt to blueprint
and no longer use the config system by the completion of Carbon.
Regards,
Brady
On 17/11/16 03:33, Colin Dixon wrote:
So, even though the file is in src/ it
