Getting 409 conflict error in inertia response

[JensvandeWiel]

[18:21:56.112] WARN: Conflict {"error":{"code":0,"internal":null,"message":null},"id":"b1f693c3-4a7e-4931-9191-85e5fc3a4fb5","request":{"host":"localhost:8080","ip":"::1","length":0,"method":"POST","params":{},"path":"/log-in","query":"","referer":"http://localhost:8080/login","route":"/log-in"},"response":{"latency":140176,"length":0,"status":409}}

Handler:

func (h *LoginInertiaHandler) ProcessLogin(ctx echo.Context) error {
	errCtx := gonertia.WithValidationError(ctx.Request().Context(), "email", "Invalid email address")
	req := ctx.Request().WithContext(errCtx)
	println(errCtx)
	i := middleware.GetInertia(ctx)
	i.Back(ctx.Response(), req)
	return nil
}

This results in a 409 conflict, am i doing anything wrong?

[JensvandeWiel]

I've learned that it only happens with i.Back()

[JensvandeWiel]

Also, this is how i make the request:

const { data, setData, post, processing, errors,  } = useForm({
        email: '',
        password: '',
    });

    const handleSubmit = (e: MouseEvent) => {
        e.preventDefault();
        post('/login');
    }

[romsar]

Looks like it's normal.
If request was made by Inertia - Gonertia set status to 409 on any redirect responses just like in official laravel adapter.
This is important for core js package, so we will not change this behaviour.

[JensvandeWiel]

Yes i understand, but how would go back to the previous page and render it with errors included. I can just call the render function but if i make more complicated handlers that have props i will need to duplicate a lot of code if i want to add errors

[JensvandeWiel]

So what is the gonertia idiomatic way to just return a response with errors back to login?

[JensvandeWiel]

Inertia-laravel uses session to store the errors and then reloads the page

[romsar]

Yup, we don't have laravel framework benefits such as session manager.
I think the best way would be to write your own implementation or use a ready-made one, for example https://github.com/alexedwards/scs (flash messages are what you need).
I don't think the solution to this problem is the responsibility of this package, but if you have an idea, feel free to express it.

upd:
I thought a little and maybe we can accept some kind of interface with only PushByUserID (id, errors) and PopByUserID (id) methods in Gonertia's constructor.
These methods will save/receive validation errors for user in redirects. PopByUserID we can put in middleware, PushByUserID we can put in gonertia.Location method.
But, we need to think about how necessary it is or it is better not to take this responsibility.

[romsar]

Draft MR that I just made: https://github.com/romsar/gonertia/pull/7/files
What do you think?

[romsar]

I just realized that the Rails adapter uses a similar scheme: https://github.com/inertiajs/inertia-rails/blob/6e0fc5a92cafd5e821e6918168260d0e2fbce539/lib/inertia_rails/controller.rb#L67

[JensvandeWiel]

Yeah, im going to use sessions since i need to implement them for auth so...

[romsar]

Check version v1.1.8. Also I updated Readme file with simple inmem example.

[JensvandeWiel]

for now this works:

func (h *LoginInertiaHandler) ProcessLogin(ctx echo.Context) error {
	errCtx := gonertia.WithValidationError(ctx.Request().Context(), "email", "Invalid email address")
	ctx.SetRequest(ctx.Request().WithContext(errCtx))
	return h.RenderLoginPage(ctx)
}

But this only works easily if the form endpoint is a subroute or the post version of the other route, since if it requires any parameters these should be available in the form submission endpoint too.

You can also use a session based system to pass errors

[romsar]

However, this is not a complete solution to the problem, I will merge https://github.com/romsar/gonertia/pull/7/files on this week, I think it will be useful.

[romsar]

Added FlashProvider in v1.1.8 version. Updated README.md.