Please share your experience with upgrade to 2.x version of JSON:API .

Should I uninstall all modules dependent on JSON:API first (jsonapi_extras, consumer_image_styles)? What if I have complex configuration of JSON:API Extras and I don't want to loose it?

I'm asking because simple composer update drupal/jsonapi --with-dependencies obviously going to update to the latest 1.x version. Should I manually change my composer.json and then run the command? Or is it best to uninstall all things and require them again?

Creating new project with composer it is a breeze but updating existing one turns to nightmare for me almost everytime =)

Huge thanks to Mateu, Gabe, Wim and all who participated in this project! You are awesome!

Comments

rozh created an issue. See original summary.

wim leers’s picture

Project: JSON:API » JSON:API Extras
Issue tags: +API-First Initiative

Great question!

What if I have complex configuration of JSON:API Extras and I don't want to loose it?

I think you should update to https://www.drupal.org/project/jsonapi_extras 2.x first, then to 3.x. But I'm not at all sure.

@e0ipso will be better able to answer this :)

logickal’s picture

We upgraded from JSON:API 1.x and JSON:API Extras 2.x (actual versions at time of upgrade were 1.23 and 2.9) by a simple

composer require drupal/jsonapi:^2.0 drupal/jsonapi_extras:^3.0, followed by the obligatory cache rebuild.

During regression we found some client and custom code issues, but nothing broke with our overrides.

wim leers’s picture

During regression we found some client and custom code issues, but nothing broke with our overrides.

That's exactly what I was hoping to hear! We definitely paid a lot of attention to making the upgrade path as smooth as possible!

Thanks a lot for chiming in with that wonderful feedback 😀

e0ipso’s picture

👏🏽 I'm glad everything went as expected Jeremy.

clemens.tolboom’s picture

Guess we can close this now?

e0ipso’s picture

Status: Active » Fixed

Yes. Thanks @clemens.tolboom!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.