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.
Problem/Motivation
\Drupal\Core\Config\ConfigFactoryInterface
has missing or generic variable types for @param
and @return
documentation.
Proposed resolution
Add types or improve existing ones.
Remaining tasks
None.
User interface changes
None.
API changes
None.
Comment | File | Size | Author |
---|---|---|---|
#10 | interdiff.txt | 364 bytes | Xano |
#10 | drupal_2191911_10.patch | 1.67 KB | Xano |
Comments
Comment #1
XanoComment #2
jhodgdonThanks!
Comment #3
dawehnerJust as little advertisment block: These changes are also part of #2184231: Use ConfigFactoryInterface to type hint ConfigFactory
+1
Comment #4
jhodgdonWell we don't need both issues/patches then, and if I commit this one it will break the other patch, right? Which one do you want to use? Please either take this stuff out of the other patch or mark this one as a duplicate.
Comment #5
XanoI merged this patch with the one from #2184231: Use ConfigFactoryInterface to type hint ConfigFactory.
Comment #6
XanoAdding these changes to #2184231: Use ConfigFactoryInterface to type hint ConfigFactory was not appreciated, so here is a new patch that no longer touches the same code as the patch in the other issue.
Comment #7
jhodgdonWhat about the rest of the patch in #1? Let's maybe wait a bit and see what eventually gets included in that other patch and what is rejected as out of scope?
Comment #8
Xano#2184231-47: Use ConfigFactoryInterface to type hint ConfigFactory indicates that all docblock changes unrelated to
@return $this
were out of scope, so I left them in that issue and removed them from the patch here.The patches no longer touch the same code and together fix all remaining docs issues.
Comment #9
jhodgdonMaybe after that one gets in, we can also fix this from that other patch then:
That needs a description added to the @return. Probably out of scope on the other issue?
Comment #10
XanoWhat do you think of this?
The other issue has been fixed, by the way.
Comment #12
jhodgdonYet another ImageFieldDisplayTest failure. Dont' bother with hitting retest, it's definitely not due to this documentation-only patch.
Anyway, this looks fine, thanks!
Comment #13
alexpottCommitted bac3a5d and pushed to 8.x. Thanks!