Skip to content

hasBlock deprecation, documenting (has-block and (has-block-params #469

@mixonic

Description

@mixonic

In working on Octane documentation I realized the following:

  • hasBlock behaves as a keyword in templates, still exists
  • (has-block is a helper which was added intending to replace hasBlock. It is suggested in the guides as best practice but has no API documentation as an Ember helper.
  • (has-block-params is often mentioned by VM developers when (has-block is 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-block API, including use for inverse blocks.
  • RFC would document/describe the (has-block-params API, 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions