Problem/Motivation
Migration missing for global settings.
Steps to reproduce
NA
Proposed resolution
Add migrations.
Remaining tasks
NA
User interface changes
NA
API changes
NA
Data model changes
NA
| Comment | File | Size | Author |
|---|---|---|---|
| #19 | interdiff_16-19.txt | 538 bytes | srishtiiee |
| #19 | migration_missing_for_global_settings-3238952-19.patch | 3.56 KB | srishtiiee |
Issue fork entity_print-3238952
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
Comment #2
srishtiiee commentedComment #3
srishtiiee commentedCorrected Kernel test for configuration migration.
Comment #4
wim leersI just have a bunch of coding style nitpicks — these are all things that in Drupal core we comply with 🙈🤓
Looking great otherwise!
Nit: missing docblock, and missing newlines before and after.
Nit: 3 newlines, should be one.
Nit: could also have the
voidreturn type!Nit: in Drupal we always write
TRUEandFALSE(all uppercase).Nit: two newlines, should be one, not two.
Nit: should have one newline between these.
Comment #5
srishtiiee commented.
Comment #6
srishtiiee commentedComment #7
wim leersOne more nitpicking round: this should be formatted using 2 spaces for each indentation level, not 4 😅
Comment #8
srishtiiee commentedComment #9
srishtiiee commentedComment #10
srishtiiee commentedComment #11
wim leersLast round probably! :D
Nit: can just be
{@inheritdoc}🤓Nit: should have no newline after the last statement and before the closing brace.
This return type hint has a space before the colon. The earlier one does not. Let's be consistent.
(Drupal core does not have a standardized style for this yet, but the majority have no space before it.
Same here.
Comment #12
karishmaamin commentedComment #13
karishmaamin commentedFix for #11 issues
Comment #14
wim leersLooking great!
Comment #15
wim leers@srishti.bankar just pointed out there are still a few unaddressed coding standards issues 🙈
Comment #16
srishtiiee commentedFixed all the coding standard issues.
Comment #17
wim leers👍
Comment #18
huzookaDrupal 7 Entity Print does not set a value for its
entity_print_default_cssvariable. This means that the variable might be completely missing from the Drupal 7varaibletable. Based on the codebase of the module, the variable's default value isTRUE.The problem is that if the
variablemigrate source plugin doesn't find a value for the given variables, it will return with a row without theentity_print_default_csssource prop being set. In this case, the migration system will set thedefault_cssdestination property toNULL, and when theentity_print.settingsis being saved, schema api will transform its value toFALSE.Solution: use the
default_valueprocess plugin with itsstrictconfig set toTRUE:Comment #19
srishtiiee commentedMade the required changes 👍🏼
Comment #20
huzookaGreat!
Comment #21
wim leersThanks, @huzooka! 😊🙏
Comment #24
vladimirausThanks.