- Issue created by @fox_01
- Merge request !22Imlementing SetIgnoreDestination and getIgnoreDestination โ (Closed) created by fox_01
- ๐ฎ๐ณIndia chetan 11
chetan 11 โ made their first commit to this issueโs fork.
- Status changed to Needs review
11 months ago 6:07am 19 December 2023 - Status changed to Needs work
11 months ago 1:53pm 19 December 2023 - ๐บ๐ธUnited States bluegeek9
$ vendor/bin/phpcs -s $_WEB_ROOT/modules/custom --report-junit=junit.xml --report-full --report-summary --report-source FILE: ...3409489/web/modules/custom/authorization-3409489/src/Form/SubFormState.php -------------------------------------------------------------------------------- FOUND 3 ERRORS AFFECTING 3 LINES -------------------------------------------------------------------------------- 849 | ERROR | [x] Line indented incorrectly; expected 2 spaces, found 3 | | (Drupal.WhiteSpace.ScopeIndent.IncorrectExact) 850 | ERROR | [x] Expected 4 space(s) before asterisk; 3 found | | (Drupal.Commenting.DocCommentAlignment.SpaceBeforeStar) 851 | ERROR | [x] Expected 4 space(s) before asterisk; 3 found | | (Drupal.Commenting.DocCommentAlignment.SpaceBeforeStar) -------------------------------------------------------------------------------- PHPCBF CAN FIX THE 3 MARKED SNIFF VIOLATIONS AUTOMATICALLY --------------------------------------------------------------------------------
- ๐บ๐ธUnited States bluegeek9
Since SubFormState is custom, and requires a main form state, maybe something like this.
/** * {@inheritdoc} */ public function setIgnoreDestination(bool $status = TRUE) { $this->mainFormState->setIgnoreDestination($status); return $this; } /** * {@inheritdoc} */ public function getIgnoreDestination(): bool { return $this->mainFormState->getIgnoreDestination(); }
- Merge request !23Issue #3409489 by bluegeek9: Fatal error: Class SubFormState contains 2... โ (Merged) created by bluegeek9
-
bluegeek9 โ
committed 8214deb9 on 8.x-1.x
Issue #3409489: Fatal error: Class SubFormState contains 2 abstract...
-
bluegeek9 โ
committed 8214deb9 on 8.x-1.x
- Status changed to Fixed
11 months ago 10:38pm 19 December 2023 Automatically closed - issue fixed for 2 weeks with no activity.