Do some basic rust parsing of functions

[QuantumEntangledAndy]

First off I apologise for my poor javascript. Not my native language.

Here I add a simple extension to add rust parsing of functions and formatting the output.

The formatted output tries to adhere to the format recommended by the rust book and the machine readable specs

Comments, suggests, outright crying over poor js code blasphemys are expected and encouraged.

Fixes: #331 Fixes: #347

[QuantumEntangledAndy]

I only seem to have it working on the docblockr:parse-tab command and not the docblockr:parse-enter, I am looking into it but suggestions would be welcome

[QuantumEntangledAndy]

Ok the reason 'extend_line': /^\s*(\/\/[\/!]?|#)/ for rust was not working in rust is because the scope is comment.block but the original code explicitly checked for comment.line I have pushed a fix on that too

[MoritzKn]

First of all, thanks for your time! Please be aware though: this package, as most of the atom eco-system, is unfortunately pretty much unmaintained. That being said if you are confident with your PR, I'd be willing to simply merge it. But if you need someone to review your work and/or help you with testing, you would need to find someone by yourself.

Please make sure that:

• the code is properly tested
• includes specs / automated tests
• debug logs / console.log are removed
• code is properly formated (whitespace, indention)

[QuantumEntangledAndy]

Yes I figured this might be unmaintained when looking at the commit histories. Just thought I'd share the changes that got it working for me.

• Testing has been done by me in rust on my own project and its holding up fine
• No specs/tests so I will look into adding that later in the week when I've got time
• Logs should be all removed but I'll double check
• I will double check the white space and maybe it though a formatter aswell

[QuantumEntangledAndy]

@MoritzKn I've gone and added the specs and have improved the rust parser to match more edge cases. I think it should be ok to merge now if you want to give it a once over.

• [x] the code is properly tested
• [x] includes specs / automated tests
• [x] debug logs / console.log are removed
• [x] code is properly formated (whitespace, indention) (via JS Beautify)

[MoritzKn]

Hi @QuantumEntangledAndy I was just getting ready to merge your PR. You've got to know I've literally didn't touch this repo in years. The thing is... the last person that worked on Docblockr was @Fluvf who did amazing work and a lot of cleaning up. I merged all of it into develop but we never got around to making a release or merging into master. So now we have a bunch of changes sitting in develop that I don't want to throw away.

The issue is if I merge your changes into master we can no longer merge develop. Would you mind rebasing (or merging) your changes against develop?

[QuantumEntangledAndy]

Sure I'll check out that branch and try a rebase. It's getting late where I am so that will have to be tomorrow now.

[QuantumEntangledAndy]

So I have a rebase ready do you want me to repoint this PR into the develop branch?

[MoritzKn]

Yes sure, you can change to the target branch. But I can do that too so it's not so important.

[QuantumEntangledAndy]

Ok done and ready

[QuantumEntangledAndy]

Ok I just saw that there was a new setting in develop that makes return and prameter doc string optional so I made a quick edit to include that in rust too :)

[QuantumEntangledAndy]

Awesome thanks for getting the merged :)

[QuantumEntangledAndy]

If you have any rusted related issues feel free to drop me an email or something

[MoritzKn]

I can't really believe it but after over 3 years I've actually just pushed a new release to the atom package registry, enjoy!

[MoritzKn]

That'd be awesome