Use OptionsProviderInterface to allow options widgets usage

Well this actually looks a bit more complex than anticipated.

If we implement OptionsProviderInterface Drupal adds a \Symfony\Component\Validator\Constraints\Choice to the field.
Which in turns, when validating the entity, calls \Drupal\jsonapi_reference\Plugin\Field\FieldType\TypedResourceObjectItem::getSettableValues

Problem : getSettableValues will only return the first 50 elements that JSON:API provides. There is then a good chance that those results, which aren't filtered using the search attribute used by the field widget, don't contain the value set for the field.

This makes validation fail :/

I'm not sure what would be the best way to handle this, since using pagination to fetch all possible values for the field would be a big hit on performance I would imagine.

Agrre that validation via pagination is prohibitive.

Let's back this out for now so we can release an alpha supporting Drupal 11.

I have reverted the change directly on the 2.0.x branch.

Hi eli-t!
Do you think it would be acceptable to remove the \Drupal\jsonapi_reference\Plugin\Field\FieldType\TypedResourceObjectItem::getConstraints call?
As it is, it only returns the AllowedValues constraint, which we do not want/can't provide for performance reasons.

We could have something like this instead https://git.drupalcode.org/issue/jsonapi_reference-3474619/-/commit/057c...

I think this is probably a good idea. Let's give it a try.

This MR does that

https://git.drupalcode.org/project/jsonapi_reference/-/merge_requests/25

This also seems to work with the additions to jsonapi_reference_field_widget_info_alter in ✨ Add select list widget Needs work and #3314975: Add radio buttons widget → .

This seems to work for me too, thanks.

Awesome - that's merged in. Let's get the two widget issues complete, update the documentation and get a new release out!

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