This issue is related to PR #2364. It could also be that my project uses TypeScript; either way, it is not actively blocking me from using the <Set> component as intended, this issue is just for DX.
When using the new private prop on the <Set> component, I'd expect unauthenticated to be a suggested prop; like it is/was for <Private>.
I'm expecting that, as I begin to type unauthenticated, it will appear as a suggestion in my IDE, much like private is.
Right now, VSCode does not suggest it, but it does know about it, and will not throw a TS error once I've fully typed out the prop's name:
A better example of what it is I'm expecting:
Thank you, as always :)
This issue is related to PR #2364. It could also be that my project uses TypeScript; either way, it is not actively blocking me from using the
<Set>component as intended, this issue is just for DX.When using the new
privateprop on the<Set>component, I'd expectunauthenticatedto be a suggested prop; like it is/was for<Private>.I'm expecting that, as I begin to type unauthenticated, it will appear as a suggestion in my IDE, much like
privateis.Right now, VSCode does not suggest it, but it does know about it, and will not throw a TS error once I've fully typed out the prop's name:
A better example of what it is I'm expecting:
Thank you, as always :)