Support placing API files in different folders about v

[JalonSolov]

This would definitely be a breaking change.

A fundamental aspect of V is that you cannot create methods on structs in other modules.

This is why all your api methods on the App struct must be in the same module as the file where your App struct is defined.

Those api methods could be tiny wrappers that simply call functions in other modules, but the main api method definition must be in the same module.

[spytheman]

I understand your concerns, but we can consider other solutions to achieve file organization and management in this way. For large projects this is very important. No one wants their code directory to be a mess

I understand your desire to organize your code in that way, but it has many disadvantages, in terms of complexity for the compiler.

[medvednikov]

I think this was suggested before. "Virtual submodules" or something. There was a long discussion on GitHub.

[medvednikov]

It can be set up via v.mod. I'm personally not against this feature, but many are against due to complications.

[Avey777]

This would definitely be a breaking change.

A fundamental aspect of V is that you cannot create methods on structs in other modules.

This is why all your api methods on the App struct must be in the same module as the file where your App struct is defined.

Those api methods could be tiny wrappers that simply call functions in other modules, but the main api method definition must be in the same module.

I understand your concerns, but we can consider other solutions to achieve file organization and management in this way. For large projects this is very important. No one wants their code directory to be a mess

[Avey777]

I imported the App and Context structures in the api module, allowing the code and no error message; but when I access this api it will return “404 Not Found”

[Avey777]

I understand your concerns, but we can consider other solutions to achieve file organization and management in this way. For large projects this is very important. No one wants their code directory to be a mess

I understand your desire to organize your code in that way, but it has many disadvantages, in terms of complexity for the compiler.

But I did this and the compiler didn't complain; I think this should be fixed.

[Avey777]

@spytheman
Are there any other roundabout ways to achieve similar code organization and management?

[Avey777]

It can be set up via v.mod. I'm personally not against this feature, but many are against due to complications.

Can you give me an example to show me how to do it

[Avey777]

It can be set up via v.mod. I'm personally not against this feature, but many are against due to complications.

Is it an implementation similar to Rust? Can you give an example?

[Avey777]

This is not possible

This is ok（This is possible, but it still doesn't achieve the purpose of putting V files in different folders）

[Avey777]

Is it possible to encapsulate it in a very concise way like go?