veb How to write api methods in different v files

[Jengro777]

module main

import x.vweb
import mall


const (
	port = 8082
)

pub struct Context {
	vweb.Context
}

pub struct App {
	vweb.Middleware[Context]
}

@["/";get;post]
pub fn (app &App) api(mut ctx Context) vweb.Result {
	eprintln('------------ ${@METHOD} -----------------')

	return ctx.json([
        "code: 200,
        message: successapi"

    ])
}


// This method will only handle GET requests to the index page
@["/";get]
pub fn (app &App) index(mut ctx Context) vweb.Result {
	eprintln('------------ ${@METHOD} -----------------')

	return ctx.json([
        "code: 200,
        message: success"

    ])
}

fn new_app() {
	eprintln('------------ ${@METHOD} -----------------')

	mut app := &App{}

	// 使用cors进行跨域处理
	// use vweb's cors middleware to handle CORS requests
	app.use(vweb.cors[Context](vweb.CorsOptions{
		// allow CORS requests from every domain
		origins: ['*']
		// allow CORS requests with the following request methods:
		allowed_methods: [.get, .head, .patch, .put, .post, .delete]
	}))

	// start our app at port 8080
	vweb.run[App, Context](mut app, port)
}


fn main(){
	new_app()
}

How to put api methods in another v file instead of main.v file

[Jengro777]

import vweb
import api {App,Context}

@["/ttt";get]
pub fn (app &App) ttt(mut ctx Context) vweb.Result {
	eprintln('------------ ${@METHOD} -----------------')

	return ctx.json([
        "code: 200,
        message: success"

    ])

}

 error: cannot define new methods on non-local type src.api.App

 @["/123";get]
 pub fn (app &App) ttt(mut ctx Context) vweb.Result {

Does this mean that I am unable to write APIs in the files of folders outside the declared App and Context structures

[JalonSolov]

That is correct. All your route methods must be in the same file.

[Jengro777]

That is correct. All your route methods must be in the same file.

why ？

[JalonSolov]

Because that's the way it's implemented? It's the way vweb works. If you want it to work differently, enter a feature request, or create a PR... however, I don't know that this has much hope of being changed, since it is similar idea to not allowing adding methods to a struct in a different module, which V will not change.

[Jengro777]

I think adding sub folders under the API folder can easily group APIs. If all are placed in the same level folder, it is very inconvenient to manage

I did this and ran the code without any errors; But when accessing the interface, it returns 404

[JalonSolov]

Closed per #21581

[Jengro777]

vproduct
    api
        api.v
    client
        client.v
    main.v

---

client.v

module client
import veb

struct Context {
	veb.Context
}

pub struct Client {}


@[get]
pub fn (app &Client) index(mut ctx Context) veb.Result {
	return ctx.json('from client')
}

---

api.v

module api

import veb
import test.client

struct Context {
	veb.Context
}

pub struct App {
	veb.Controller
}

pub fn (app &App) index(mut ctx Context) veb.Result {
	return ctx.text('from app')
}

pub struct Admin {}

@[get]
pub fn (app &Admin) index(mut ctx Context, id int) veb.Result {
	return ctx.text('from admin ${id}')
}

pub struct Foo {}

pub fn (app &Foo) index(mut ctx Context) veb.Result {
	return ctx.text('from foo')
}

pub fn  start() {
	mut app := &App{}
	register_routes(mut app)
	veb.run[App, Context](mut app, 9090)
}

fn register_routes(mut app App){

  mut admin_app := &Admin{}
  app.register_controller[Admin, Context]('/admin', mut admin_app) or {panic(err)}

  mut foo_app := &Foo{}
  app.register_controller[Foo, Context]('/foo', mut foo_app)or {panic(err)}

  app.register_controller[client.Client, Context]('/client', mut &client.Client{})or {panic(err)}
}

---

mian.v

module main

import api {start}
fn main() {
	start()
}

[Jengro777]

Using Controller, you can organize API code across modules (multiple folders)

[Jengro777]

@JalonSolov I have organized the API code in different modules through controllers, but each API method needs to define a new structure. This method is a bit cumbersome. Is there a simpler way?