Brysen LaBute

Results 9 comments of Brysen LaBute

@TheSpicyMeatball curious your thoughts on this when you get a chance!

> > Found a temporary fix/workaround - wrap the node which contains a possible undefined value in a fragment component. For example: `{value && {value}}` Thanks for the suggestion! It...

@alleksei37, I shared [this message](https://github.com/TheSpicyMeatball/react-nanny/issues/18#issuecomment-1298497004) on the initial issue in case you are looking for alternatives.

Good afternoon! My team recently ran into this as well but we added a `.vsls.json` file in our workspace to prevent folks from seeing or editing the `.vscode/settings.json` file [per...

This is similar to https://github.com/figma/code-connect/issues/215 but i am unsure if this will be resolved at the same time.

Hello! Just checking in on this one. Thank you

Hello @slees-figma! Thanks for the information. We look forward to that functionality! Somewhat related, does `nestedProps` support using a wildcard (`*`) for the `layerName` like `children` does? We've got a...

Thanks, @slees-figma! I appreciate the quick response! In case anyone comes across this and the feature is not yet available, as a workaround, my team is: 1. Using `nestedProps` and...

Good day! After some more testing, it appears that this issue only occurs in the "Playground" of Figma. If just in the Code Connect view, it works as expected.