feat(vlang): create module

[Milo123459]

Description

Adds a module to display the currently installed V version

Motivation and Context

Closes #

Screenshots (if appropriate):

How Has This Been Tested?

• I have tested using MacOS
• I have tested using Linux
• I have tested using Windows

Checklist:

• I have updated the documentation accordingly.
• I have updated the tests accordingly.

[vladimyr]

Following the precedent established by golang let's use vlang instead. Leaving that aside, good job @Milo123459 👍

[vladimyr]

V uses v.mod files following Go's go.mod approach. @Milo123459 do a quick investigation to find out whether there are additional package management related files with v.sum being a likely candidate.

[Milo123459]

Question, does detect_extensions have to always have that, but also have all the required files?
For example, would:
hello.v without v.mod display?
Or would it need hello.v & v.mod to display?

[Milo123459]

May as well add a version system for V.

[vladimyr]

Question, does detect_extensions have to always have that, but also have all the required files?
For example, would:
hello.v without v.mod display?
Or would it need hello.v & v.mod to display?

If any of the conditions are met module will get displayed so it is OR rather than AND.

[vladimyr]

May as well add a version system for V.

Now I lost you. What do you mean by version system?

[Milo123459]

May as well add a version system for V.

Now I lost you. What do you mean by version system?

I updated the package module to display the V version if v.mod is present.

[vladimyr]

LGTM 🚀

[vladimyr]

@Milo123459 Please apply this patch https://github.com/vladimyr/starship/commit/8dcd68f.patch

[Milo123459]

So I'm changing the vlang config to v? I don't know why but sure

[vladimyr]

So I'm changing the vlang config to v? I don't know why but sure

Honestly, this is not my invention 🙃 There is already a Go module that sets precedent by having src/configs/go.rs and src/modules/golang.rs. And as much as it may be the wrong one I'll always try to keep (naming) consistency. That being said I have zero objections to a new PR that changes both golang, vlang, you name it to use more natural filenames but it has to be consistent across the board. 😉

[vladimyr]

@Milo123459 Once again thanks for your patience and hard work!

LGTM 🚀

[Milo123459]

Anything else need to change?

[andytom]

Thank you for your contribution @Milo123459 and thank you for reviewing @vladimyr and @davidkna