Prevent fallback to text-based completions when completing object properties with unknown declared type
Open
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
**Bicep version**
Unknown
**Describe the bug**
This is related to #14065. We appear to be falling back to text-based completions.

**To Reproduce**
n/a
**Additional context**
n/a
Contributor guide
Research direction
Start by reading the related issue #14065 and reviewing the attached completion example. No source files, tests, or reproduction steps are named, so locate the object-property completion entry point before determining how unknown declared types are handled. Done means text-based completions are no longer used for this case and the behavior is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100