Work out a concept for dict setting completions

Open
#157 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
tooling

Research direction

Start by reviewing the existing value-completion behavior described in this issue, including completions from default values, comments, and list items. Read related issue #156 and the referenced commit for context. Done means there is an agreed concept for handling dictionaries, including nested or list-contained values and unhashable types.

Written by the indexing model from the issue text.

Description

enhancement for later consideration

Currently, we just ignore dicts when offering value completions, because

  1. we don't know how to handle them in most situations, especially when they occur as secondary values inside a list,
  2. our architecture can't handle unhashable type (and we have special handling for lists)

Completions currently originate from either the default value, parsing comments and indirectly from list items of a default list value. Currently it seems only completing the default value it sensible.

Related: #156, 2fba8f54d98145f9c9965b7689dbdeb0ec160b28

Dominant language
Python
Stars
455
Forks
86
Avg merge
7d 10h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SublimeText/PackageDev

All issues in SublimeText/PackageDev

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.