Closed fredemmott closed 4 years ago
Also probably worth special-casing the id
attribute the same way transferAttributesToRenderedRoot does - if both set and !=, it's probably a bug
This might end up being "deprecate for new code" instead of remove - e.g.
return <foo>...</foo>
, replace with return <foo {...$this}>...</foo>
use IXHPWithImplicitCopy_DEPRECATED
or similar
Originally expected to remove this from v3.x due to the introduction of XHP attribute splat - announced with https://github.com/hhvm/xhp-lib/releases/tag/v2.6.0
This has some behavior behavior, e.g:
Additionally, this is causing problems with #135 - after render has started, setAttribute, forceAttribute, removeAttribute etc must error.