Suggestion: stable internal param names, to allow for non-disruptive parameter renames

My understanding is that renaming a parameter for sync tables effectively deletes the old one and adds a new one (unless they are postion-based). It would be nice to be able to define stable names for parameters that can be used internally, and then also provide some display name that can be renamed without disrupting existing usages.

Thanks for the feedback @loucadufault, it’s something I’ve wanted as well! At the moment required parameters are positional, and can be renamed without breaking anything. Optional parameters though can be referenced by name, and so renaming them is a breaking change.

I’ll pass this on to the engineering team for consideration, but I expect it may be a lot of work and likely won’t be available in any near term.

1 Like