Skip to content
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

more explorative tests for webc:for #161

Merged
merged 1 commit into from
Apr 6, 2023
Merged

more explorative tests for webc:for #161

merged 1 commit into from
Apr 6, 2023

Conversation

sombriks
Copy link
Contributor

@sombriks sombriks commented Apr 5, 2023

i was trying to build that scenario for the issue i was facing, however i am not sure anymore if it's a issue at all.

i did this testcase, please merge it if it worth anything.

i'll try to apply what i learned doing it on my faulty code, see if the issue was, once again, between the keyboard and the chair ;-)

@zachleat
Copy link
Member

zachleat commented Apr 5, 2023

Just so I understand, this is testing aliasing the loop item as a separate variable name?

@lsilveira-boku
Copy link

Just so I understand, this is testing aliasing the loop item as a separate variable name?

yes, and nesting loops too.

it works perfectly, the issue i saw must be related to my use on my blog, not to webc itself.

on a smaller note, i got access to the variable created by for inside one of the components, however they are inside the default slot, so i think this is expected.

it was a very clean way to understand my problem, an the test suite is quite nice to read and understand.

@zachleat zachleat merged commit ac5f607 into 11ty:main Apr 6, 2023
@zachleat zachleat added this to the WebC v0.11.3 milestone Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants