Tom Duncalf

Hi @andreiduca, thanks for raising this and for such a clear explanation of the use case. I agree that this would make sense – I'm going to raise this topic...

Hey, thanks for your interest in Code Connect! We’re planning to add support for more frameworks in the near future. We can’t say yet exactly which frameworks or when, but...

Hey, thanks for your interest in Code Connect! We’re planning to add support for more frameworks in the near future. We can’t say yet exactly which frameworks or when, but...

Hey, thanks for your interest in Code Connect! We’re planning to add support for more frameworks in the near future. We can’t say yet exactly which frameworks or when, but...

Hey, thanks for your interest in Code Connect! We’re planning to add support for more frameworks in the near future. We can’t say yet exactly which frameworks or when, but...

Hey @vchandran8! You're right, this isn't supported right now, only the prop value itself can reference `props`. It sounds like it would be useful for us to support this for...

This will be fixed in the next release @vchandran8

Hi @l-campbell, right now we don't support this I'm afraid, but it's on our roadmap as we know some design system do use overrides like this instead of props. I'll...

Cool, thank you! Yeah, in our case we are doing something in response to the secret changing, so with the current behaviour we have to have both a change listener...

Hey @BeFunes - I just mean something like: ``` context.secrets.onDidChange(e => { handleSecretsDidChange(); }); function handleSecretsDidChange() { // do stuff } function somethingWhichUpdatesSecrets() { context.secrets.store("whatever", "secret"); handleSecretsDidChange(); // This won't...