Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
menu_block.schema.yml defines "expanded".
MenuBlock::defaultConfiguration() defines "expand".
Looks like it got changed at some point, but the default config wasn't updated...
Comment | File | Size | Author |
---|---|---|---|
#16 | interdiff_2932048-14-16.txt | 420 bytes | rajeevk |
#16 | 2932048-16.patch | 881 bytes | rajeevk |
#14 | 2932048-14.patch | 461 bytes | Prashant.c |
#12 | 2932048-12.patch | 420 bytes | harsha012 |
#4 | patch-clean.png | 29.87 KB | Maheshwaran.j |
Comments
Comment #2
pingers CreditAttribution: pingers as a volunteer and at University of Adelaide commentedHere's a patch.
Comment #3
Maheshwaran.j CreditAttribution: Maheshwaran.j as a volunteer and at DrupalPartners for Innoppl Technologies Pvt. Ltd commentedComment #4
Maheshwaran.j CreditAttribution: Maheshwaran.j as a volunteer and at DrupalPartners for Innoppl Technologies Pvt. Ltd commentedHi Pingers
Your Patch applies cleanly for version 8.x-1.x. Please refer the screenshot.I have no idea why your patch did not go through automated testing.
Comment #5
Maheshwaran.j CreditAttribution: Maheshwaran.j as a volunteer and at DrupalPartners for Innoppl Technologies Pvt. Ltd commentedComment #6
pingers CreditAttribution: pingers as a volunteer and at University of Adelaide commentedThere's a simpler answer than you might think... there are no 8.x-1.x tests.
Comment #7
Maheshwaran.j CreditAttribution: Maheshwaran.j as a volunteer and at DrupalPartners for Innoppl Technologies Pvt. Ltd commentedPingers
So only Core modules go through automated testing? Every dev versions of a module do not go through the testing.?
Comment #8
pingers CreditAttribution: pingers as a volunteer and at University of Adelaide commentedContrib modules go through testing... if there are tests for the module :)
See http://cgit.drupalcode.org/menu_block/tree/src - there are no tests to run.
Comment #9
Maheshwaran.j CreditAttribution: Maheshwaran.j as a volunteer and at DrupalPartners for Innoppl Technologies Pvt. Ltd commentedThanks .! :) Now I understand how it works.
Comment #10
Maheshwaran.j CreditAttribution: Maheshwaran.j as a volunteer and at DrupalPartners for Innoppl Technologies Pvt. Ltd commentedComment #11
joelpittetIt looks like we should change the schema from 'expanded' to 'expand' because we are using 'expand' everywhere else.
Comment #12
harsha012 CreditAttribution: harsha012 as a volunteer and commentedfixed as per #11
Comment #13
joelpittetthanks @harsha012 here's the docs on how to make a schema change:
https://www.drupal.org/docs/8/api/update-api/updating-configuration-in-d...
We need to get an update hook for existing sites.
Feel free to disagree with me on the name change, I can't think which is best, just seemed like less work to go to 'expand'
Comment #14
Prashant.c@joelpittet
I have just started learning the Config system so tried my hands for updating the Config Object name PFA.
Please let me know if this is the correct way and will it work ?.
Comment #15
rajeevkLatest patch (#15) missing change in configuration schema YML file. Changing to need work..
Comment #16
rajeevkComment #17
joelpittetThis looks great, if someone can give it a quick review and test, I'll commit.
Comment #18
Dinesh18 CreditAttribution: Dinesh18 as a volunteer commentedI have tested the patch manually and it looks good to me.
+1 to RTBC
Comment #20
joelpittetThank you I've pushed this to the latest dev branch.
Comment #22
Chris Matthews CreditAttribution: Chris Matthews as a volunteer commented