-
Notifications
You must be signed in to change notification settings - Fork 92
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
Zowe Explorer should be programming language agnostic #3131
Comments
Thank you for creating a bug report. |
Thank you for raising this enhancement request. |
Research Needed: Investigate backwards compatible implementation with possible toggle/switch setting. Note: If we change the behavior of removing the extensions, that will shift some of the responsibility to the LSPs for detecting the language in open editor. |
Describe the bug
Zowe Explorer provides access to z/OS resources such as MVS data sets and PDS members. You can click on a member to open it in the default VS Code text editor. With its excellent SDK it provides a fantastic platform for extenders to layer their capabilities on top of Zowe Explorer. Zowe Explorer's scope imho is not to provide language specific capabilities such as syntax highlighting or code completion. It therefore needs to be designed language agnostic and not make any assumption about the content of an MVS, USS, or spool file. This would be the responsibility of Zowe Explorer extender extensions to interpret content and decide special behavior such as assuming a program language. Zowe Explorer right now looks at data set names and appends file extensions based on hard coded rules not allowing extenders to control for themselves how a file should be treated.
To Reproduce
IBMUSER.SAMPLE.COBOL
.cbl
file extension preventing a JCL language server VS Code extension to appropriately interpret its contents.Expected behavior
Zowe Explorer should not make any assumptions about the files it opens; other than encodings in UNIX file tags etc.
Screenshots
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: