vieter-v
/
v
2
0
Fork 0
Code Issues Pull Requests Releases Activity
v/vlib/v/tests/project_with_modules_having...
History
Enzo 2de1437a1e
ci: vet all files from the compiler (#5994) 		2020-07-27 12:15:29 +02:00
..
bin ci: vet all files from the compiler (#5994) 2020-07-27 12:15:29 +02:00
mod1 move compiler tests from compiler/ to v/ 2020-03-27 18:01:46 +01:00
tests ci: vet all files from the compiler (#5994) 2020-07-27 12:15:29 +02:00
.gitignore move compiler tests from compiler/ to v/ 2020-03-27 18:01:46 +01:00
README.md move compiler tests from compiler/ to v/ 2020-03-27 18:01:46 +01:00
v.mod doc: use `v new` instead of `v create` 2020-06-14 21:20:31 +03:00

README.md

This projects demonstrates how v.mod lookup can be used so that a project/module can be as selfcontained as possible.

The programs under bin/ can find the modules mod1, because the project has a 'v.mod' file, so v module lookup for the programs under bin/ can still find the parent sibling folder mod1/ through relation to the parent 'v.mod' file.

Note also that mod1/ also has its own 'v.mod' file. This allows mod1 submodules to find and import themselves in relation to it too.

Finally, there is a test/ folder, so you can put all your tests in there, without cluttering your top level folder, or your module folders if you so desire.