Marcin Jastrzebski

We need to update the link from the aka.ms bicep types issue link and will also need to create an issue template or form in the bicep-types-az repo.

This is really cool!

Agree. If telemetry shows no meaningful usage, we should remove.

There's something wrong with binding. The below doesn't compile: ```bicep metadata test = 2 param test string output test string = 's' var foo = test ``` Metadata should behave...

> > There's something wrong with binding. The below doesn't compile: > > ```bicep > > metadata test = 2 > > param test string > > output test string...

I looked into it a little bit. In `main` it's going through TypeAssignmentVisitor.VisitMissingDeclarationSyntax and finding a binding for the decorator function. In your branch it's not finding a binding for...

I like this. When I was converting our internal templates, I had to manually look for these and probably missed some.

Depending on how we do this, it could end up being a breaking change as well.

I agree. I ran into this issue, and it was somewhat workflow-breaking to have to manually delete the file.

I think the easiest and most consistent option here would be to add support for the `@secure()` decorator to outputs. (I don't think we should introduce the type modifier syntax...