Azure / Azure/bicep

Paste as bicep: Can we create new files directly in the editor for modules from nested templates?

Open
#9,847 0 comments 0 reactions 0 assignees View on GitHub
devdiv Needs: Upvote
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

from #1759

Right now, if you use context menu to decompile a bicep file that contains nested templates, it creates new module files on disk for those templates. But not if you paste as Bicep (you get a module reference, but the file does not exist).

Bicep discussion decided best solution is probably to create new files in the editor for the modules, and have them be unsaved.

Contributor guide

Open the contributing guide

Research direction

Compare the existing context-menu decompile behavior with Paste as Bicep for nested templates, focusing on how module references are created. Done means Paste as Bicep creates the referenced module files as unsaved editor files, matching the proposed Bicep discussion outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.