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

Better intellisense suggestions in VS Code #1446

Closed
NeverHere opened this issue Feb 3, 2021 · 3 comments
Closed

Better intellisense suggestions in VS Code #1446

NeverHere opened this issue Feb 3, 2021 · 3 comments
Milestone

Comments

@NeverHere
Copy link

Is your feature request related to a problem? Please describe.
I do not have a lot of previous experience with ARM templates, I am starting my declarative journey with Bicep. With that out of the way, I find myself reviewing examples of ARM Templates or the resources on docs.microsoft.com to re-write what I want in Bicep. I also decompile a lot of existing ARM templates into Bicep.

Describe the solution you'd like
I would like to have some sort of description in VS Code when creating a new resource that tells me parameters are available for use for that resource instead of parameters that are just required, most items only require a name, location, and resource group to deploy but many other parameters are needed to actually deploy the resource.

@NeverHere NeverHere added the enhancement New feature or request label Feb 3, 2021
@ghost ghost added the Needs: Triage 🔍 label Feb 3, 2021
@alex-frankel
Copy link
Collaborator

Are you using the Bicep VS Code extension? That uses the resource API specifications to determine which properties are available and required and it will show these in intellisense. For example, you can see things like this:

image

image

We also have an outstanding issue (#804) to "scaffold" resources based on this info, so you don't have to type out each property individually.

@NeverHere
Copy link
Author

Here is my example, you can see the actual bicep file on the left and the example on the right. Is this an issue where the options are just not available in intellisense yet?

image

This is helpful but I would agree that #804 is likely to be more helpful in the future.

@majastrz
Copy link
Member

majastrz commented Feb 4, 2021

All the properties in IntelliSense come from swaggers. I think these are the most likely culprits:

  • These properties aren't declared in the swagger
  • Our swagger processing logic has a bug that causes these properties to be excluded
  • IntelliSense is not handling the type information correctly

We will investigate what is happening with this resource type.

@alex-frankel alex-frankel added this to the v0.4 milestone Feb 10, 2021
@alex-frankel alex-frankel modified the milestones: v0.4, v0.5 Jun 3, 2021
@ghost ghost locked as resolved and limited conversation to collaborators May 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants