-
-
Notifications
You must be signed in to change notification settings - Fork 405
Closed
Description
In working on Octane documentation I realized the following:
hasBlockbehaves as a keyword in templates, still exists(has-blockis a helper which was added intending to replacehasBlock. It is suggested in the guides as best practice but has no API documentation as an Ember helper.(has-block-paramsis often mentioned by VM developers when(has-blockis being discussed, however this is also not documented as a public API.- AFAICT there has been no RFC that got us here
I'd like to propose an RFC which would resolve this loose end:
- RFC would document/describe the
(has-blockAPI, including use for inverse blocks. - RFC would document/describe the
(has-block-paramsAPI, including use for inverse blocks. - RFC would require that we document the same as API.
- RFC would propose and document a deprecation for
hasBlock
This is related to #460 (@wycats on named blocks) as I believe these APIs will have a lot more use and prominence once named blocks land.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels