Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spec out how extensions provide settings to us #122

Open
Tracked by #100
zadjii-msft opened this issue Oct 28, 2024 · 0 comments
Open
Tracked by #100

Spec out how extensions provide settings to us #122

zadjii-msft opened this issue Oct 28, 2024 · 0 comments
Labels
Area-API Anything having to do with the actual interface the extensions use to communicate with the host Issue-Task

Comments

@zadjii-msft
Copy link
Owner

This is one third of #100. We need to write up the spec for what the API looks like for extensions to provide uniform settings to us.


Current plan of record:

  • ICommandProvider has an ICommandSettings property on it
  • ICommandSettings just has one property, IFormPage SettingsPage
    • We'll use that form page as what we render
  • Then, we'll also provide a rich library to abstract out working with individual settings (so everyone doesn't need to write JSON handlers themselves)
@zadjii-msft zadjii-msft added the Area-API Anything having to do with the actual interface the extensions use to communicate with the host label Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-API Anything having to do with the actual interface the extensions use to communicate with the host Issue-Task
Projects
None yet
Development

No branches or pull requests

1 participant