Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This went in #2308745: Remove rest.settings.yml, use rest_resource config entities in 8.2.0-beta1 (https://www.drupal.org/project/drupal/releases/8.2.0-beta1) and I think we have now rest_resource config entities instead of having them on rest.settings.yml so I think a lot of work needs to be done to generate and manage the config entities now.
More details in https://www.drupal.org/node/2667736/
Comments
Comment #2
pcambraI see that the latest -dev version supports this, yay!, would it make sense to separate this in a 2.x branch?
Comment #3
clemens.tolboomIn #2758563-34: Handle core 8.2.x changing REST configuration to use configuration entities @dawehner reasoned
which I agree. We can always increment the system dependencie as I did in http://cgit.drupalcode.org/restui/diff/restui.info.yml?id=ada367e
@pcambra does that answers your branch question?
Comment #4
pcambraThanks for the feedback :) I just found confusing that the "git version" is compatible with 8.2 and the rest are 8.1... probably releasing a 1.13 at least would be useful as it is not clear that there's a 8.2 compatible version here
Comment #5
clemens.tolboomI've been thing about a release to.
(I'm curious how many D8.0 / D8.1 users will try to update to this new version and will that break their site?)
New release configured https://www.drupal.org/project/restui/releases/8.x-1.13
Comment #6
pcambraWouldn't this prevent them from upgrading:
- system (>=8.2.0)
Maybe inforce a hook_requirements on update (it still exists in D8?) phase?
Comment #7
clemens.tolboomI've updated lots of incompatible modules in the past ... the D7 way was on install time. Not sure how D8 does it. And no time to waste on testing that.