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

Default setting for the python language, and others which use the # and @ symbols in their syntax and markup #6469

Closed
NellyWhads opened this issue Nov 10, 2024 · 3 comments
Assignees
Labels
feature-request Request for new features or functionality
Milestone

Comments

@NellyWhads
Copy link
Contributor

The default settings explicitly disable all feature for the python language: Python is excluded from issue and user autocompletion.
I understand the syntax collision between python decorators and code comments, however, python is not the only language which uses these symbols in its syntax and markup.

Suggested fixes:

  1. Disable the default python language exceptions, at least for the @ symbol to be consistent with all other languages
  2. Allow users to configure the extension to work in comments only, or make this the default behavior
    • The extension will behave consistently across all languages
    • Each language will need a (hopefully default) configuration for parsing comment/markup symbols
    • This should automatically be handled by the language support extensions, but I am not a VSCode expert
  • Extension version: v0.98.0
  • VSCode Version: 1.93.1 (Cursor)
  • OS: MacOS Sonoma 14.5 (23F79)
  • Repository Clone Configuration (single repository/fork of an upstream repository): single repository, no submodules
  • Github Product (Github.com/Github Enterprise version x.x.x): github.com

Steps to Reproduce:

  1. Install extension and log in
  2. Make python file
  3. Attempt to use the extension's # and @ autocomplete features in the python file.
@alexr00 alexr00 added the feature-request Request for new features or functionality label Dec 2, 2024
@NellyWhads
Copy link
Contributor Author

Are contributors encouraged to make PRs to this repo?

@alexr00
Copy link
Member

alexr00 commented Dec 9, 2024

Yes, PRs are absolutely welcome! This week and next week in particular are a good time for community PRs too as we're we've started our annual clean up, which means I'll look at community PRs more quickly. Let me know if you want any code pointers.

@NellyWhads
Copy link
Contributor Author

@alexr00 PR is linked and pushed - how might I implement any additional tests, if necessary?

@alexr00 alexr00 self-assigned this Dec 13, 2024
@alexr00 alexr00 added this to the January 2025 milestone Dec 13, 2024
@alexr00 alexr00 closed this as completed Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants