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

Should we move to support multiple languages? #17

Closed
neild3r opened this issue Mar 24, 2017 · 11 comments
Closed

Should we move to support multiple languages? #17

neild3r opened this issue Mar 24, 2017 · 11 comments
Labels

Comments

@neild3r
Copy link
Owner

neild3r commented Mar 24, 2017

It wouldn't be that hard to support additional languages? Few things worth noting.

  • Already a docblockr that works well with js/typescript so should we bother with that?
  • What other languages should be included?
  • We probably need people to contribute their languages so better code documentation would be required
  • Limits how deep we can go improving the PHP support, or does it? Can we move to tokenizers within each language in future?
  • Could we somehow leverage the syntax highlighting to help us parse code to make it easier to port to other languages?
  • How do we handle the rename of the extension.
@Xety
Copy link

Xety commented Apr 27, 2017

If would be nice if it could work for the Zephir lang. It's very similar to PHP.
https://zephir-lang.com

@neild3r
Copy link
Owner Author

neild3r commented Apr 27, 2017

I'm familiar with it, I've done some work on Phalcon in the past, good suggestion.

@joelday
Copy link

joelday commented Aug 24, 2017

@neild3r I have a private branch where I was working on a multi-language solution for vscode-docthis. There are some interesting challenges for sure. Been too busy to go forward with it much.

@lmajano
Copy link

lmajano commented Sep 26, 2017

I would love to help with ColdFusion/CFML support

@ta-riq
Copy link

ta-riq commented Jan 23, 2018

Can i help to convert my favorite extension to my native language ?

Bangla

@mbourd
Copy link

mbourd commented Feb 24, 2018

  • Ungroup parameters tags and return tag

  • Add tags for class and namespace such as :

Nice extension

@darighteous1
Copy link

darighteous1 commented Mar 12, 2018

Custom tags and coloring options would be nice. For example, I'd like to color dock blocks in a custom color to stand out. Currently, they show as a multi-line comment.

@nezaboravi
Copy link

Possibility to keep @return tag as last tag in docblock.

@kAlvaro
Copy link

kAlvaro commented Aug 27, 2018

I particularly prefer addons that do one thing and do it well. As of today this is the PHP docblock extension that seems to works best and it still can use improvements in certain areas (such as @throws generation). Just my opinion ;-)

@joseffb-mla
Copy link

Add custom @Used-By tag and have the extension scour the code to autofill references. Would also like it to do this for the @uses tag as well.

@televators
Copy link

@joseffb-mla Same! I know I'm dredging old issues but I am getting into documenting my stuff better and using phpDocumentor and they support the @Used-By tag as well as @uses and generates links between all associated structures in the documentation it creates. Plus having both @uses and @Used-By would provide some contextual data for other plugins to use in interpreting and jumping around.

@neild3r neild3r closed this as completed Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests