-
-
Notifications
You must be signed in to change notification settings - Fork 496
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
Eleventy computed data consuming collections #1114
Comments
Sorry about this! Some huge changes to computed data have happened recently but a beta hasn’t shipped with those yet. Can you retest with |
My code is in a slightly broken state r/n, but a quick check off of Thanks for the quick reply! Love computed data, an excellent addition to 11ty! |
Ok! I've gone ahead and tested this and it is in fact not rendering as expected, although this may be a different issue (and if it is I'm happy to open up a separate issue). It feels like computed data isn't hooked up to collections yet. Now that objects and This was all tested in |
Thanks for your patience here—can you retest with the latest master? |
Huzzah! Thank you so much for the work on this! It does appear as if it's working as expected now! 😁 |
Yay! Really appreciate you testing—thanks! I’ll ship a new beta shortly. |
Describe the bug
Computed data doesn't seem to work for outputting an object or
true
(but oddly enough,false
works fine). Instead, an erroroutput.split is not a function
is thrownTo Reproduce
eleventyComputed.js
file in the global data directory.data => true
. Note the erroroutput.split is not a function
data => ({})
. Note the erroroutput.split is not a function
Expected behavior
Expect to be able to set a computed property to either
true
or an object.Environment:
Additional context
I expect this to work from the Advanced Details section.
The text was updated successfully, but these errors were encountered: