The results of an web.EventFunc could be:

• Go to a new page
• Reload the whole current page
• Refresh part of the current page

Let's demonstrate reload the whole current page:

import (
	"fmt"
	"time"

	"github.com/qor5/web/v3"
	. "github.com/theplant/htmlgo"
)

var count int

func ReloadWithFlash(ctx *web.EventContext) (pr web.PageResponse, err error) {
	var msg HTMLComponent

	if d, ok := ctx.Flash.(*Data1); ok {
		msg = Div().Text(d.Msg).Style("border: 5px solid orange;")
	} else {
		count = 0
	}

	pr.Body = Div(
		H1("Whole Page Reload With a Flash"),
		msg,
		Div().Text(time.Now().Format(time.RFC3339Nano)),
		Button("Do Something").
			Attr("@click", web.POST().EventFunc("update2").Go()),
	)
	return
}

type Data1 struct {
	Msg string
}

func update2(ctx *web.EventContext) (er web.EventResponse, err error) {
	count++
	ctx.Flash = &Data1{Msg: fmt.Sprintf("The page is reloaded: %d", count)}
	er.Reload = true
	return
}

var ReloadWithFlashPB = web.Page(ReloadWithFlash).EventFunc("update2", update2)

var ReloadWithFlashPath = URLPathByFunc(ReloadWithFlash)

ctx.Flash Object is used to pass data between web.EventFunc to web.PageFunc just after the event func is executed. quite similar to Rails's Flash. Different is here you can pass in any complicated struct. as long as the page func to use that flash properly.

er.Reload = true tells it will reload the whole page by running page func again, and with the result's body to replace the browser's html content. the event func and page func are executed in one AJAX request in the server.