Support placing API files in different folders

[Avey777]

Describe the feature

#21196

Use Case

If I store all api files in a single folder, as the number of apis increases, the organization and management of the files will become very confusing.

Proposed Solution

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Version used

0.4.6

Environment details (OS name and version, etc.)

macos
linux
windows

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

[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.

[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”

[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.

[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?

[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]

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?

[Avey777]

@["/1688_form/";post]
pub fn (app &App) pf1688_form(mut ctx Context, offer_id_i64 i64) veb.Result {
	log.info("执行函数:${@METHOD} ${@MOD}.${@FILE_LINE}")

	if offer_id_i64 <= 0 {
		eprintln(offer_id_i64)
		return ctx.json({"code": "100", "msg": "offer_id 必须是整数"})
	}

	sqldata := mall_1688(offer_id_i64) or { return ctx.json({"code": "102", "msg": "数据库链接错误"}) }
	if sqldata.len == 0 {
		return ctx.json({"code": "103", "msg": "数据库查询失败"})
	}

	return ctx.json(sqldata[0])
}

Is this type of encapsulated code block still too large, can it be encapsulated the same as the one mentioned above? One line is an API
@JalonSolov

[nkev]

This issue is the only reason we don't build website backends and APIs with V. We use Go instead.
It's a fundamental requirement to organize handlers into own logical modules, like we can in any other language.

[medvednikov]

@nkev V and Go have a very similar modular system. Can you please elaborate what Go allows you to do that V doesn't?

[nkev]

@medvednikov Sure. The Go code from Avey777 above shows the issue well with gt_path.Translation whereTranslation is the handler and gt_path is a separate imported Go package.

It's very convenient to separate all the routes from main.v into a separate package, but I could never do it in vweb when I last tried last year.

So from main.v I would like to call the package routes.init_router() to initialize all routes, like this:

If this is possible with veb we would love to see an example.

[medvednikov]

I see, yes it's now possible in veb using controllers:

    mut api_controller := &other_module.Api{
        db: app.db
    }
    app.register_controller[Api, Context]('/api', mut api_controller)!
    app.use(veb.cors[Context](cors_options))