emberjs/ember.js

Invalid uses of `{{outlet}}` should throw

Open

#18,547 opened on Nov 15, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (22,437 stars) (4,216 forks)batch import
Help WantedRouting

Description

  1. Using {{outlet}} in anything other than a route template (e.g. components)
  2. Using {{outlet}} inside the application template of a non-routable engine ({{mount}})

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Ember's template systemFamiliarity with Ember routes and engines
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Look into the Ember.js source code, specifically the template compiler and rendering engine. Identify where `{{outlet}}` is currently handled. Investigate if there are existing validation checks for similar constructs (e.g., `{{component}}`). The goal is to add a warning or error when `{{outlet}}` is used outside a route template or in a non routable engine's application template. Consider adding tests to ensure the new validation works. Relevant files might be in `packages/@ember/ internals/glimmer/lib/` or similar. The issue has no linked PRs or comments, so no prior work to reference.
Invalid uses of `{{outlet}}` should throw · emberjs/ember.js#18547 | Good First Issue