Specify default JSON:API Extras enhancers link fields globally

READMES/jsonapi.md

@@ -48,3 +48,34 @@ You can find JSON:API tests in the following places:
 
 - 'tests/phpunit/API/JsonApiRequestTest' - Tests GET requests and associated configuration.
 - 'tests/phpunit/API/JsonApiExplorerUITest' - Tests Swagger UI for OpenAPI documentation.
+
+## Field Type Enhancers
+
+JSON:API Extras allows "field enhancers" to change the normalized output sent back in a response. These are set in
+configuration on "/admin/config/services/jsonapi/resource_types", but there is no way to use current configuration
+and code to set a default field enhancer for all field instances of the same field type. We are calling this feature
+"field type enhancers" to contrast with the current field instance enhancers tied to resources.
+
+On "/admin/config/services/jsonapi/field_types", we added a configuration form where you can add a field type
+enhancer that will apply to all fields of that type. However, if you set a field instance enhancer, that will
+override the field type enhancer. So, users can set an enhancer for most of the field instances of one field type
+but then customize each field instance as needed.
+
+This custom code is in a patch, but we are trying to incorporate it into the main `jsonapi_extras` module in this issue:
+https://www.drupal.org/project/jsonapi_extras/issues/3025283
+
+To use the field instance enhancers:
+
+1. Go to "/admin/config/services/jsonapi/resource_types" and click to edit the resource type you are working with.
+2. Check the fields you want alter output for to see if they already have an enhancer applied.
+3. If there is an enhancer configured for that field instance, then that is what will be used for JSON:API responses.
+4. If you want to use a field type enhancer, remove the configured field instance enhancer.
+
+To use the field type enhancers:
+
+1. Go to "/admin/config/services/jsonapi/field_types" and check the "Included Field Types" text area.
+2. If you see your field added and have an enhancer configuration form visible, then skip to step #4.
+3. If the field isn't included, then add it to the textarea and save the form.
+4. Adjust the enhancer type and settings to achieve the output you want for that field type and save the form.
+5. All field types should now be transformed by the selected enhancer for JSON:API responses, unless a field
+   instance enhancer is overriding the field type enhancer.

composer.json

@@ -451,6 +451,9 @@
                 "3226473 - Opt-in system delete.": "https://www.drupal.org/files/issues/2023-03-28/3226473-opt-in-system-delete-2.patch",
                 "3061620 - Cancel closes all forms": "https://www.drupal.org/files/issues/2022-07-21/inline_entity_form-close-only-forms-where-close-clicked-3061620-13.patch"
             },
+            "drupal/jsonapi_extras": {
+                "3025283 - Default field enhancer for each field type": "patches/field-type-enhancer-3025283-3.patch"
+            },
             "drupal/jsonapi_menu_items": {
                 "3276561 - Add support for the Menu Item Extras module": "https://www.drupal.org/files/issues/2022-08-01/3276561-05-menu_item_extras_support.patch"
             },

composer.lock

@@ -4,7 +4,7 @@
         "Read more about it at https://getcomposer.org/doc/01-basic-usage.md#installing-dependencies",
         "This file is @generated automatically"
     ],
-    "content-hash": "c9df9e950f406065f385e866e17e4a72",
+    "content-hash": "e9a118f67eb61dfb52ad2120983a525f",
     "packages": [
         {
             "name": "asm89/stack-cors",

config/sync/jsonapi_extras.jsonapi_field_type_config.yml

@@ -0,0 +1,12 @@
+disabled: false
+resourceFields:
+  link:
+    fieldName: link
+    enhancer:
+      id: url_link
+      settings:
+        absolute_url: 0
+type: config_entity
+label: 'JSON:API Field Type Config'
+includedFieldTypes:
+  - link