Have gr.on set value at start as well

[aliabid94]

If you have a demo like this:

with gr.Blocks() as demo:
    a = gr.Number(1)
    b = gr.Number(1)
    c = gr.Number()

    @gr.on(inputs=[a,b], outputs=c)
    def add(x,y):
        return x + y

demo.launch()

c will only be set to the value of a + b when they change, not initially when the demo runs. Usually users would want the initial value to also be a function of the inputs (when no trigger is specified).

This is also consistent with the behaviour of gr.render and value=fn, e.g. both of these would set c to 2 intitially:

with gr.Blocks() as demo:
    a = gr.Number(1)
    b = gr.Number(1)

    @gr.render(inputs=[a, b])
    def renderfn(x, y):
        gr.Number(x + y)

demo.launch()

with gr.Blocks() as demo:
    a = gr.Number(1)
    b = gr.Number(1)
    c = gr.Number(lambda x, y: x + y, inputs=[a, b])

demo.launch()

Technically breaking so going into 5.0

[gradio-pr-bot]

🪼 branch checks and previews

•	Name	Status	URL
	Website	ready!	Website preview

[abidlabs]

lgtm one note above