Skip to content

Commit 6bc9379

Browse files
manvkaurCopilot
andcommitted
chore: add .gitignore with out/ exclusion
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 1eea341 commit 6bc9379

2 files changed

Lines changed: 13 additions & 12 deletions

File tree

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
out/

proposed/templates-e2e.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -7,37 +7,37 @@
77

88
---
99

10-
## Command Verb — Decision Required
10+
## Command Verb — Under Discussion
1111

12-
> **This decision drives the rest of the document.** The verb chosen here determines the command or subcommand name, class names, CLI surface, and whether it collides with the in-flight templates workload.
12+
> **This decision drives the rest of the document.** The verb chosen here determines the command name, class names, CLI surface, and whether it collides with the in-flight templates workload.
1313
14-
This design proposes **`templates`** as the subcommand verb (`func new templates`). However, there is a naming conflict: a separate templates workload is in flight that provides templating (engine, parameterization, etc.). Using `templates` for this command risks conceptual and CLI-surface collision with that workload.
14+
Development is proceeding with **`quickstart`** as the working name. This is a **top-level command** (`func quickstart`) delivered as a workload — not a subcommand of `func new`. The final verb is still under discussion.
1515

1616
| Candidate | Full Command | Subcommands | Pros | Cons |
1717
| --- | --- | --- | --- | --- |
18-
| **`templates`** (proposed) | `func new templates` | `list`, `info` | Familiar term; matches industry use for e2e prod ready apps | Collides with templates workload; |
19-
| **`sample`** | `func new sample` | `list`, `info` | These are sample repos; no overloading of "template" | Might imply "not production-ready" |
20-
| **`quickstart`** | `func quickstart` | `list`, `info` | Clear intent; aligns with Azure Samples naming (`*-quickstart-*-azd`) | Longer to type; top-level only (not under `func new`) |
21-
| **`bootstrap`** | `func new bootstrap` | `list`, `info` | Accurate for "set up a project from scratch" | Less discoverable; not a common Azure CLI verb |
22-
| **`clone`** | `func new clone` | `list`, `info` | Technically accurate (it clones a repo) | Implies git; doesn't convey curation or discovery |
18+
| **`quickstart`** (working name) | `func quickstart` | `list`, `info` | Clear intent; aligns with Azure Samples naming (`*-quickstart-*-azd`); top-level; no collision with templates workload | Longer to type; may imply "beginner-only" and limit room for advanced samples |
19+
| **`templates`** | `func templates` | `list`, `info` | Industry standard (Vercel, bolt.new, AZD Templates, AI Template Gallery all use "templates"); VS Code extension already calls it "Template Gallery"; doesn't limit scope to quickstarts | Collides conceptually with in-flight templates workload that provides parameterized per-function scaffolding |
20+
| **`sample`** | `func sample` | `list`, `info` | These are sample repos; no overloading of "template" | Might imply "not production-ready" |
21+
| **`bootstrap`** | `func bootstrap` | `list`, `info` | Accurate for "set up a project from scratch" | Less discoverable; not a common Azure CLI verb |
2322

24-
**Recommendation:** `templates` — this is the industry used term for scaffolding a new project, including production-ready starting points. We will need resolve conflict with the in-flight templates workload and establish distinction.
25-
26-
> **Impact of verb change:** The verb is used in the subcommand name, class names (`TemplatesCommand``SampleCommand`), service names, and all CLI examples throughout this document. The design is otherwise identical regardless of verb chosen. Swapping the verb is a find-and-replace — no architectural changes.
23+
> **Impact of verb change:** The verb is used in the command name, class names (`QuickstartCommand``TemplatesCommand`), service names, and all CLI examples throughout this document. The design is otherwise identical regardless of verb chosen. Swapping the verb is a find-and-replace — no architectural changes.
2724
2825
---
2926

3027
## Table of Contents
3128

32-
- [Command Verb — Decision Required](#command-verb--decision-required)
29+
- [Command Verb — Under Discussion](#command-verb--under-discussion)
3330
- [Problem Statement](#problem-statement)
3431
- [Goals / Non-Goals](#goals--non-goals)
3532
- [Proposed Design](#proposed-design)
3633
- [Command Tree](#command-tree)
3734
- [New Services](#new-services)
3835
- [ITemplateManifestService](#itemplatemanifestservice)
36+
- [Release & Compliance Model](#release--compliance-model)
3937
- [Runtime-to-Language Mapping](#runtime-to-language-mapping)
4038
- [ITemplateFunctionScaffolder](#itemplatefunctionscaffolder)
39+
- [Download Strategy](#download-strategy---fetch-githttp)
40+
- [Git Process Requirements](#git-process-requirements)
4141
- [User Experience Flow](#user-experience-flow)
4242
- [Execution Flow](#execution-flow)
4343
- [Manifest Cache Flow](#manifest-cache-flow)

0 commit comments

Comments
 (0)