-
Notifications
You must be signed in to change notification settings - Fork 479
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
@ helper's don't work #776
Comments
I have similar issue with Node.js 8.8.1 version
|
We are facing the same issue as mentioned by @hegdeashwin |
yeah. It's blocking us to migrate to node 8 |
@kumarrishav have fixed the node 8 bug here ... |
I'll give it a look :)
On Thu, Dec 7, 2017, 6:30 AM Ashwin Hegde ***@***.***> wrote:
@kumarrishav <https://github.com/kumarrishav> have fixed the node 8 bug
here <LinkedInAttic/dustjs-helpers#146> ...
can anyone please help us to merge the PR?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#776 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABVa7BNlcq0SmmPA3slBN3IYkOeCb0CKks5s9_aQgaJpZM4PcVOO>
.
--
Sent while mobile
|
Is this nested structure supposed to work?
feed.dust
event.dust
Inside the partial
event
none of the @ helpers function correctly. If I output {counter} or do a context dump the correct value appears. In case it was a type issue I added a string property with a static value and did an @eq test on it which also failed to produce output. {:else} blocks are also not displayed it's as if the entire condition is stripped somehow.Is this a bug? If I change the @select in the parent view to @eq checks the @ helpers inside
event
do function as you'd expect them to. The reason it's an @select is because there are about 10 different views depending on the value of category.The text was updated successfully, but these errors were encountered: