Azure / Azure/azure-functions-core-tools

Follow-ups for .func/config.json (PR #5010)

Open
#5,011 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
1.5k
Forks
498
Avg merge
5d 4h
Merged PRs (30d)
15

Description

Follow-ups deferred from PR #5010 (`.func/config.json` bare-minimum scaffold). Tracking here so we don't lose them.

### Deferred items

- [ ] **Mismatch warning** when `.func/config.json` disagrees with resolver auto-detection (today we trust config silently).
- [ ] **`InitCommand` reads config** to seed selection (today init writes config but doesn't read it).
- [ ] **`$schema` URL + JSON schema file** published for editor IntelliSense.
- [ ] **`.gitignore` template** updates so transient `.func/` artifacts (state, logs, azurite data) are ignored while `.func/config.json` is committed.
- [ ] **README / `docs/` updates** documenting the file, schema, and precedence chain.
- [ ] **Standalone E2E test** covering the full precedence chain (`--stack` > `.func/config.json` > host.json gate > `FUNCTIONS_WORKER_RUNTIME` > resolver claims).
- [ ] **Per-workload extension area** in the schema, **walk-up discovery** from cwd, and **mirroring to `main` / `in-proc` branches**.

PR: #5010

Contributor guide

Open the contributing guide

Research direction

Review the deferred-items checklist for .func/config.json, InitCommand, host.json, FUNCTIONS_WORKER_RUNTIME, README/docs, and the standalone E2E test. Start by determining which item can be scoped independently; done means its corresponding schema, precedence behavior, ignore rules, documentation, or test is implemented and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
cli, cloud, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.