Closed tpiperatgod closed 2 years ago
Currently, functions-framework-go needs to handle three different functions:
func(http.ResponseWriter, *http.Request)
func(context.Context, cloudevents.Event) error
func(*ofctx.OpenFunctionContext, []byte) ofctx.RetValue
This is not user-friendly and is not conducive to maintenance and evolution.
Use functions(unified function signatures) based on the openfunction functions-framework specification to support different functions.
Agree
Close via https://github.com/OpenFunction/functions-framework-go/pull/22
Motivation
Currently, functions-framework-go needs to handle three different functions:
func(http.ResponseWriter, *http.Request)
func(context.Context, cloudevents.Event) error
func(*ofctx.OpenFunctionContext, []byte) ofctx.RetValue
This is not user-friendly and is not conducive to maintenance and evolution.
Main goal
Use functions(unified function signatures) based on the openfunction functions-framework specification to support different functions.