Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
documentation
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
2 Feb 2015 at 14:15 UTC
Updated:
17 Feb 2015 at 16:54 UTC
Jump to comment: Most recent
Comments
Comment #1
dawehnerFair
Comment #2
wim leersRTBC++
Comment #3
alexpottI don't think the
|nullis necessary.(optional)is enough. I think hyper paranoid world is covered by the typehint.Comment #4
martin107 commentedPlease forgive me, I disagree
"|null" is something my subconscious brain, seems to look out for.
My imperfect brain reads the current line, perfectly.
( And I don't want to degrade the original intent of #2099741: Protect WYSIWYG Editors from XSS Without Destroying User Data )
I just wanted some tools I use to be more correctly informed ... so I won't be applying the changes.
Closing the issue as won't fix works for me.
Comment #5
alexpottThis is still a docs bug
Comment #6
wim leers#3: I'm also confused why you say that; we do it that way all over core? This is about typehints, and according to http://php.net/manual/en/function.gettype.php,
NULLis its own type. A typehint should indicate all possible types. NULL is its own type. So… why not add it?Comment #7
alexpottOkay never mind me - I'm wrong. Still then the (optional) looks optional.
Comment #8
alexpottDocs fixes are not subject to beta evaluation. Committed a160367 and pushed to 8.0.x. Thanks!