New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@error directive #747

Closed
chriseppstein opened this Issue May 11, 2013 · 5 comments

Comments

Projects
None yet
7 participants
@chriseppstein
Member

chriseppstein commented May 11, 2013

Users should be able to create an error with @error <message>

@nex3 nex3 referenced this issue Oct 24, 2013

Closed

@error directive #983

@xzyfer

This comment has been minimized.

Show comment
Hide comment
@xzyfer

xzyfer Dec 6, 2013

Contributor

👍 At the moment we work around this issue by emitting a warning a returning null since null'd properties are omitted from output. Although comes with it's own confusion.

Contributor

xzyfer commented Dec 6, 2013

👍 At the moment we work around this issue by emitting a warning a returning null since null'd properties are omitted from output. Although comes with it's own confusion.

@danielcreid

This comment has been minimized.

Show comment
Hide comment
@danielcreid

danielcreid May 6, 2014

Any news on the status of this? Would be a great feature to have.

danielcreid commented May 6, 2014

Any news on the status of this? Would be a great feature to have.

@manikrathee

This comment has been minimized.

Show comment
Hide comment
@manikrathee

manikrathee May 6, 2014

+1 on this - it would be a huge gain for large teams.

Writing a complex animation mixin and I want to throw a verbose error when the mixin fails so anyone on the team can understand the issue right away.

manikrathee commented May 6, 2014

+1 on this - it would be a huge gain for large teams.

Writing a complex animation mixin and I want to throw a verbose error when the mixin fails so anyone on the team can understand the issue right away.

@apfelbox

This comment has been minimized.

Show comment
Hide comment
@apfelbox

apfelbox May 7, 2014

Contributor

👍

Contributor

apfelbox commented May 7, 2014

👍

@battaglr

This comment has been minimized.

Show comment
Hide comment
@battaglr

battaglr Jun 17, 2014

This also would be great to avoid doing this over and over:

@warn <message>;
@return false; // Or `null`.

@chriseppstein: how do you plan @error to work?

battaglr commented Jun 17, 2014

This also would be great to avoid doing this over and over:

@warn <message>;
@return false; // Or `null`.

@chriseppstein: how do you plan @error to work?

@chriseppstein chriseppstein added this to the 3.4 milestone Jul 12, 2014

nex3 added a commit that referenced this issue Jul 12, 2014

@nex3 nex3 closed this Jul 12, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment