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

Include deno.enablePatterns on config schema #126

Closed
wants to merge 2 commits into from

Conversation

turadg
Copy link

@turadg turadg commented Aug 10, 2020

A new config option, deno.enablePatterns, was added in #92. The config schema wasn't added, probably because there's no UI editor for "array" type. However, it's still worth defining.

  1. To avoid this confusing message:

Screen Shot 2020-08-09 at 5 31 18 PM

  1. To get an indication in the Settings UI that the key exists and can be edited in the JSON:

Other types, such as object and array, aren't exposed directly in the settings UI, and can only be modified by editing the JSON directly. Instead of controls for editing them, users will see a link to Edit in settings.json as shown in the screenshot above.

A new config option, `deno.enablePatterns`, was added in denoland#92. The [config schema](https://code.visualstudio.com/api/references/contribution-points#contributes.configuration) wasn't added, probably because there's no UI editor for "array" type. However, it's still worth defining.

1. To avoid this misleading feedback:

2. To get an indication in the Settings UI that the key exists and can be edited in the JSON:
> Other types, such as object and array, aren't exposed directly in the settings UI, and can only be modified by editing the JSON directly. Instead of controls for editing them, users will see a link to Edit in settings.json as shown in the screenshot above.
Copy link
Member

@ry ry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@ry
Copy link
Member

ry commented Aug 14, 2020

Please merge with master

@David-Else
Copy link

David-Else commented Aug 16, 2020

@turadg @ry I think #92 was wiped out in the recent merge so this PR is now invalid, but someone should confirm that.

@turadg
Copy link
Author

turadg commented Aug 16, 2020

@David-Else thanks for pointing out that #125 wiped out the enablePatterns feature @Flaque created in #92.

That feature is essential in codebases that mix Deno and non-Deno code.

@bartlomieju would you accept it again?

@bartlomieju
Copy link
Member

@turadg sure! Sorry I didn't carry it over

@turadg
Copy link
Author

turadg commented Aug 21, 2020

Closing this since it doesn't make sense without #153 as in included in that.

@turadg turadg closed this Aug 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants