Problem :
In radix.info.yml file

regions:
  navbar_branding: 'Navbar branding'
  navbar_left:  'Navbar left'
  navbar_right: 'Navbar right'
  content: Content
  footer: Footer

content and footer is not in proper format.

Solution :
As per the drupal.org guidelines , https://www.drupal.org/docs/8/theming-drupal-8/adding-regions-to-a-theme

 content: 'Content'
 footer: 'Footer'

Both the above should be in single quote

Comments

Dinesh18 created an issue. See original summary.

darshan.addweb’s picture

Status: Active » Needs review
StatusFileSize
new345 bytes

@Dinesh18, Please find the patch with your required changes & let me know if any further changes are required.

dinesh18’s picture

Looks good to me. Let's wait for the maintainer to check & commit. Thanks

akash.addweb’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new37.41 KB

@ritika.addweb, Thanks for the patch, your patch works as per the expected standards. I checked and compared it with the standards mentioned in attached screenshot

morbus iff’s picture

Updating this to 4.x and including the kits' .info.yml.

jacine’s picture

Category: Bug report » Feature request

While, I agree it is nice to wrap them all in quotes for consistency, this page is not a "guideline". It is simply documentation. And this issue is not a bug report.

See all of the core themes that implement regions, they only quote the names that have more than one word:

- https://git.drupalcode.org/project/drupal/blob/8.8.x/core/themes/seven/s...
- https://git.drupalcode.org/project/drupal/blob/8.8.x/core/themes/bartik/...

ckng’s picture

Quoting is not needed in YAML for these cases. It is not a standard to have quote here. Personally prefer no quotes.
See https://www.yaml.info/learn/quote.html

  • ckng committed 3361045 on 8.x-3.x
    Issue #2985139 by Morbus Iff, ckng: Standardized regions naming...
ckng’s picture

Version: 8.x-3.2 » 8.x-3.x-dev
Status: Reviewed & tested by the community » Fixed

This was standardized as no quote in 4.x, doing the same here for 3.x.

Status: Fixed » Closed (fixed)

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