improve debugging possibilities of error messages

Open
#23 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Start by reproducing the error when the did-insert function is invalid, then trace the modifier's error path from that entry point. Improve the resulting message with enough context to identify the modifier key and component or nearby DOM node, and verify the error is useful across the application.

Written by the indexing model from the issue text.

Description

image

If passed fn for did-insert is not an function, it's literally udebuggable across application (there is no mentions of key name, component name, closest dom node and such)

Dominant language
TypeScript
Stars
86
Forks
34
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 emberjs/ember-render-modifiers

All issues in emberjs/ember-render-modifiers

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.