Add category for DGI image discovery field type

[bibliophileaxe]

While creating fields, the DGI Image Discovery field appears as Taxonomy Term.

Re: https://islandora.slack.com/archives/CM5PPAV28/p1756247387293879

Summary by CodeRabbit

• New Features

  • Introduced a new field type category, “DGI Image Discovery,” with a label and description to improve admin selection and organization.
  • Related image fields are grouped under this category and set to appear lower in lists for consistent placement.

• Chores

  • Updated minimum platform core requirement to 10.2 (affects compatibility/upgrade planning).

[coderabbitai]

Walkthrough

Adds a new field type category configuration, updates the DIDImageItem field type plugin annotation to use that category, and bumps the module core_version_requirement; no executable code or API signatures were changed.

Changes

Cohort / File(s)	Summary
Field type category config config/.../dgi_image_discovery.field_type_categories.yml	Introduces dgi_image_discovery category with label "DGI Image Discovery", description "An image relevant to the given node.", and weight 100.
Field type plugin annotation src/Plugin/Field/FieldType/DIDImageItem.php	Adds category = "dgi_image_discovery" to the FieldType annotation; no code or signature changes.
Module info dgi_image_discovery.info.yml	Updates core_version_requirement from `^9

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I hop through fields of YAML bright,
A new category set just right.
Plugins now find their proper place,
Metadata hugged with gentle grace.
Carrot-stamp: discovery, in sight! 🥕

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)

• JIRA integration encountered authorization issues. Please disconnect and reconnect the integration in the CodeRabbit UI.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bugfix

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b469bac and 7e6998a.

📒 Files selected for processing (2)

• dgi_image_discovery.field_type_categories.yml (1 hunks)
• src/Plugin/Field/FieldType/DIDImageItem.php (1 hunks)

🔇 Additional comments (3)

dgi_image_discovery.field_type_categories.yml (1)

1-4: Category config looks correct and matches the plugin annotation ID.

Label/description/weight are sensible. No functional concerns.

src/Plugin/Field/FieldType/DIDImageItem.php (2)

15-23: Good addition: FieldType categorized for Field UI.

category = "dgi_image_discovery" correctly aligns with the new category ID.

---

21-21: Guard against older-core breakage.

The "category" key isn’t recognized by older Drupal versions and could trigger an annotation exception. Ensure your supported core range excludes unsupported versions (update core_version_requirement if necessary).

If updating, add to your .info.yml:

core_version_requirement: ^10.2

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

dgi_image_discovery.info.yml (1)

5-5: Confirm necessity of ^10.2 and consider widening to Drupal 11.

If the new field type category requires APIs introduced in Drupal 10.2, this bump is justified. If the module also runs on Drupal 11, widen the constraint to avoid blocking adopters.

Proposed change:

-core_version_requirement: ^10.2
+core_version_requirement: ^10.2 || ^11

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7e6998a and 8657bd9.

📒 Files selected for processing (1)

• dgi_image_discovery.info.yml (1 hunks)

[adam-vessey]

This seems to promote/support the idea of adding a separate copy of this computed field beyond the base field we inject, but this should really never be necessary? #38 makes things go away more completely.