- @tnakai opened merge request.
マージリクエストを作成しました。
Drupal Contribution Day Tokyo 2025にて以下のメンバーと共に作業しました。
- Jimmy Cann
- tnakai
- @zonepotage
- dc-mkinoshita- @yrkf opened merge request.
- First commit to issue fork.
- Issue created by @tnakai
- Issue created by @yrkf
- Issue created by @tnakai
- 🇦🇺Australia jimmycann
Created this issue as part of Drupal Contribution Day Japan 2025
- Issue created by @jimmycann
- 🇺🇸United States xenophyle
Thanks for submitting this ticket — and sorry we didn’t get back to you about it sooner. We are cleaning up old issues and issue for old versions and are going to close this one. If this issue is still relevant for you, please re-open it and update the “Version” field, and include any updates to the behavior you are seeing.With a smaller issue queue, we’ll have an easier time getting back to you.
- 🇧🇪Belgium yorickdv
Thank you for the review.
However, I believe there may be a misunderstanding about the architecture. This module implements global configuration, not plugin-specific configuration.
The IgnoreFieldsSettingsForm is a module-level settings form that saves to tmgmt_ignore_fields.settings.yml and affects all tmgmt translation jobs site-wide. This is the correct pattern for global module configuration using ConfigFormBase.
The c pattern you mentioned applies to plugin-specific configuration where each plugin instance needs its own settings, which is not the case here. This module provides a single global setting that determines which fields to ignore for all translation jobs.
Automatically closed - issue fixed for 2 weeks with no activity.