Skip to content

Unable to handle and recover from invalid user configuration #53

@ufukty

Description

@ufukty

Context

  • Refactors the config pipeline and fixes improper access to language-specific configuration #50 revealed omits incorrect user configs and Prompt user for semantic issues on user configuration #52 filed a suggestion to correct.
  • During the refactor of improving the organization between config reader, compiler, cache store, editor decorator and the extension lifecycle controller, I realized it is not obvious how the initialization of an editor decorator should proceed when there is a such incorrect user config problem.
  • The ambiguity is sourced from the uncertainty of whether the incorrect config prompts should be handled at a centralized place (over the individual editor decorators) in order to avoid prompting the user repeatedly.
  • In case of the prompting handled at a centralized place (above the decorators, eg. the lifecycle controller) then the partial initialization of decorators should be settled.

Problem

Refactor is blocked.

Suggestion

  • Settle the decision on how the config errors handled and implement changes accordingly.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions