Functions Payload Structure discussion #801
mahatoankitkumar
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Payload Structure Versioning Plan
v1.0 Payload Structures
Future v2.0 (Example)
Current (multiple parameters)
New (single payload object)
Add payload_version column to functions table
Default value: "1.0"
Modify FunctionType::get_fn_signature() to accept version parameter
Store signatures for all versions and provide as per the version mentioned in the database
Support multiple versions in match statements for signatures
Add payload_version field to function create/update endpoints (optional, defaults to latest)
All existing functions automatically get payload_version = "1.0"
Payload format remains identical (backward compatible)
Can add new fields in v2.0 without breaking v1.0 users
Users migrate when ready
Multiple versions coexist
Beta Was this translation helpful? Give feedback.
All reactions