[ckan-dev] extensions decoupling: ckan.model, get_action & metadata

[David Raznick]

> we discussed this a bit at the dev meetup.  The problem was that giving
> access to model ties our hands quite a bit for example the Package.to_dict
> function may get removed - kindly is keen to do this or at least was at one
> point.  If it's available via plugins.toolkit we promise to not break the
> `api` so I don't want to do that.
> Plugins can still just import ckan.model but if they do this then we do not
> agree not to break them.  If they connect via plugins.toolkit then they
> should not be breaking however much we refactor core
> So anything in toolkit becomes a long term support commitment so we need to
> be careful

I agree with this approach.  It would be very good to discourage the
use of model directly but it will inevitably be needed by some (at
their or our own risk).  The complexity and diligence needed to make
sure we never break an extension that is using the model directly is
too much.


I am happy with this general direction.