meteor / meteor/blaze

Help developers by indicating undefined data in debug mode

Open
#365 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
543
Forks
117
Avg merge
6h 18m
Merged PRs (30d)
2

Description

It would be great to implement a debug mode that could be enabled by default in development mode (via `process.env` or `Meteor.isDevelopment` ?) that adds logging messages when a variable is not defined in a template.

As an example the following code
```


{{title}}

```
could raise console info messages on render when `title` is not defined in `Template.instance().data` or not defined in template helpers or when the helper return an undefined value

I think this feature could be helpful for developers, specially when refactoring code

Do you think it would be doable without too much effect on performance ? Maybe this could be done with custom code outside of blaze core ?

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified. Start by locating Blaze's template rendering and helper/data lookup paths, then determine how a development-only debug mode could report undefined template data or helper results without affecting production behavior; done means the proposed cases produce console info messages with acceptable performance impact.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.