Problem/Motivation

The schema is at schema/rare.schema.yml:1, but Drupal discovers module config schema from config/schema/*.schema.yml. Because this module has no config/schema/rare.schema.yml, rare.settings likely has no discovered schema.

Steps to reproduce

  1. Install RARE in Drupal 11.x.
  2. Run: drush config:inspect --detail --only-error
--------------- ----------- ------------- ------ 
  Key             Status      Validatable   Data  
 --------------- ----------- ------------- ------ 
  rare.settings   No schema                       
 --------------- ----------- ------------- ------ 

Expected

Expected: rare.settings uses the schema from rare.schema.yml.

Actual

schema is not discovered because the file is under schema/, not config/schema/.

Proposed resolution

Move the schema file from:

schema/rare.schema.yml

to:

config/schema/rare.schema.yml

Issue fork rare-3606705

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

dkmishra created an issue. See original summary.

nakaza sora’s picture

Assigned: Unassigned » nakaza sora

nakaza sora’s picture

Status: Active » Needs review

Created an MR that moves the schema file to config/schema/ so the rare.settings schema is discovered. Ready for review — thanks!

nakaza sora’s picture

Assigned: nakaza sora » Unassigned
dkmishra’s picture

I tested commit `2efce592` from the MR by running `drush config:inspect --detail --only-error`, and I can confirm that it no longer reports any missing schema issues.

Tested and RTBC +1.

boroughbee’s picture

@nakaza sora and @dkmishra much appreciated for pointing this out, will update module with your contribution, once tested as soon as possible.

  • nakaza sora committed 2efce592 on 1.0.0
    Issue #3606705: Move config schema file to config/schema directory
    
boroughbee’s picture

Thanks to sora nakaza and dkmishra. Merged. v1.0.1

dkmishra’s picture

Thanks for merging this, @boroughbee! Just a couple of small follow-ups:

The issue status is still showing Needs review. Since the fix has now landed in 1.0.1 via commit `2efce592`, could you please update the issue status to Fixed?

Also, could you please add the appropriate contributor credit to the commit? I don’t see it reflected in the contribution record yet.

Thanks again for the quick turnaround and for getting this fix included in the release!

boroughbee’s picture

Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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