Problem/Motivation

We could have extra test coverage, following berdir's steps to reproduce in #2803179-10: [regression] rest_update_8201() can fail and break things

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

catch created an issue. See original summary.

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers at Acquia commented
Title: Additional test coverage for rest_update_82019) » Additional test coverage for rest_update_8201()

So… I'm not sure what you would like to see happen here, considering you said

Theoretically we could have update tests for this, but it'd be a lot of work compared to what is equivalent to “use the literal schema definition instead of hook_schema()”

I guess this is to determine whether we do want test coverage for this after all?

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner as a volunteer and at Chapter Three commented

IMHO its always worth to write tests, sometimes it just has a lower priority give the costs vs. profits.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers at Acquia commented
Issue summary: View changes
Status: Active » Closed (won't fix)

After six months there have been zero additional bug reports about this. We can always add more tests indeed, but the cost of this has been shown to not outweigh the benefits.

I think it's fine to "won't fix" this issue at this point.