Preprocessor not processing co-located components for engine

Open
#106 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
build-system

Research direction

Start by reproducing the engine configuration described in the issue, including podModulePrefix for routes and standard component locations. Trace how the preprocessor registry collects templates for routes versus components; done means the engine's preprocessor receives both co-located template types.

Written by the indexing model from the issue text.

Description

I have an engine registering a preprocessor for its own template files. It receives all templates for routes but none of the templates for components.

The route templates are co-located with the route js files by setting the podModulePrefix.
The component templates are co-located with the component js files using standard component location.

The above configuration works for apps and engines otherwise, but could be part of the trouble here. I'd note though that addons that add a preprocessor for the engine get access to both, so I suspect the issue is elsewhere.

Dominant language
JavaScript
Stars
1
Forks
11
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ember-cli/ember-cli-preprocess-registry

All issues in ember-cli/ember-cli-preprocess-registry

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.