You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using the web editor but find the documentation to be outdated and the lack of autocompletion makes it unnecessarily difficult to get started.
So I looked for an alternative and found TS declaration files. The following script reads the relevant Java files in this repository and creates declarations which in turn provide type inference and autocompletion.
This is merely a proof-of-concept, expect wrong/generic types, missing method arguments, class boundary violations (nested classes), ...
I'm not familiar with Java, so I won't go any further with this, but you should have no trouble adjusting your documentation export to produce something along these lines.
The text was updated successfully, but these errors were encountered:
For people not familiar with Python, the easiest way to run this is: python -m pip install pipenv; python -m pipenv run pip install javalang; python -m pipenv run python ./get_ts_declarations.py .
Hi @notEvil this sounds really amazing! This for sure will help to update the old docs,
I will have to check how to integrate it in the ace editor that PHONK uses.
I'm a bit busy atm but I will try this and answer your other questions by the end of next week.
Thanks!
Hi,
I've been using the web editor but find the documentation to be outdated and the lack of autocompletion makes it unnecessarily difficult to get started.
So I looked for an alternative and found TS declaration files. The following script reads the relevant Java files in this repository and creates declarations which in turn provide type inference and autocompletion.
https://gitlab.com/-/snippets/2482545
In Neovim with Ycm
This is merely a proof-of-concept, expect wrong/generic types, missing method arguments, class boundary violations (nested classes), ...
I'm not familiar with Java, so I won't go any further with this, but you should have no trouble adjusting your documentation export to produce something along these lines.
The text was updated successfully, but these errors were encountered: