pouyakary / comment Goto Github PK

Hi,

any way you could support Terraform Files?

Comments take the Form of either // or # (Terraform Docs)

But I think the # is the preffered method to comment.

Thanks for this really cool project!

I am getting this error when trying to update to version 23. I am currently on version 22.

2023-03-27 08:09:54.046 [error] ENOENT: no such file or directory, open 'c:\Users\MyUserName\.vscode\extensions\.43a79c12-55b8-4e1d-bd07-514d6631eeca\Icon .original': Extract: ENOENT: no such file or directory, open 'c:\Users\MyUserName\.vscode\extensions\.43a79c12-55b8-4e1d-bd07-514d6631eeca\Icon .original' at x.u (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:15438) at async x.extractUserExtension (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:12665) at async X.u (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:19248) at async X.x (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20836) at async X.h (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)

The comments can be single-line, started with a # character, or inline/multi-line, enclosed within /* ... */.

Hi,

Thanks for the addon. It would be great if it supports Pine Script.

File extension: *.pine
Comment Syntax: //

Example:

// Comment
var grpAdx = "Trend"

Kind Regards,

This plugin now can support C++ but not support C.

I hope this plugin can support C too, thanks!

Is the website https://kcs.library.kary.us/ permanently down or is their a new web address to learn more about this standard ?

I am getting this error when trying to update to version 23. I am currently on version 22.

2023-03-27 08:09:54.046 [error] ENOENT: no such file or directory, open 'c:\Users\MyUserName\.vscode\extensions\.43a79c12-55b8-4e1d-bd07-514d6631eeca\Icon .original': Extract: ENOENT: no such file or directory, open 'c:\Users\MyUserName\.vscode\extensions\.43a79c12-55b8-4e1d-bd07-514d6631eeca\Icon .original' at x.u (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:15438) at async x.extractUserExtension (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:12665) at async X.u (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:19248) at async X.x (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20836) at async X.h (vscode-file://vscode-app/c:/Users/MyUserName/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)

would you be able to add vbscript to the available languages for your plugin?

Hello, the extension is incredible, please add the inline-comment in this way.

and only the first character is with capital letter, the others in minuscule

With this could have better explanation of the code without adding much space, please add this feature 🙏

Hi there, this extension is great but unfortunately it doesnt work with the majority of file types I work with. Is there any chance you could add support for alternative filetypes through support for this kind of package.json adjustment:

        "languages": [
            {
                "id": "qmd",
                "extensions": [".qmd"],
                "aliases": ["QMD", "qmd"]
            }
        ],

From the installed extension files, seems like the source for the plugin is from:
http://codes.kary.us/comment/vscode/blob/master/dictionary.js#L35 as below,

return {
    sensitive: false,
    chars: { start: "//", middle: "//", end: "//" },
}

While the source code below hosted on github, on the other hand contains:
https://github.com/pmkary/comment-vscode/blob/master/dictionary.js#L33

return {
    sensitive:  false,
    chars: { start: "#", middle: "#", end: "#" },
}

Comment generated from a .js file within React is shown below:

//
// ─── JS COMMENT IN REACT ────────────────────────────────────────
//

From what is actually generated, I'm assuming the correct chars are the one from codes.kary.us. Should the github repository be updated to reflect that (if this repository is still maintained)?

At the moment there's no support for the .rego policy language which is the OPA’s (Open Policy Agent) native query language

Comments in rego are in the form:

# ------ some policy ------

Is there anyway to support .vue files?

Thanks for the wonderful project!

Hi all,

Since the new version, the header comment are no longer capitalized. I tried looking into the settings to find how to do this but couldn't.

Is this on purpose ? If so, is there any way to add this as an option ?

Thanks for your help !

Can we also get support for sql?

At the moment your dictionary has case "css":, but it does not have a case "scss":.
SASS files can have the same format of comments as .js files within React!

Comment generated from a .js file within React is shown below:

//
// ─── JS COMMENT IN REACT ────────────────────────────────────────
//

Also, I think you need two cases for SASS files, one for case "scss": (syntax using curly brackets) and the other for case "sass": (indented syntax)

Return object for the above cases to be added in the dictionary:

return {
    sensitive: false,
    chars: { start: "//", middle: "//", end: "//" },
}

Any chance this could be added?