-
Notifications
You must be signed in to change notification settings - Fork 887
chore: use static params when dynamic param metadata is missing #17836
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Dynamic & static code flow is now independent
@aslilac I took your suggestion and it is way cleaner 👍
The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
closer! still some issues tho
}) | ||
} | ||
|
||
func (api *API) handleParameterWebsocket(rw http.ResponseWriter, r *http.Request, render previewFunction) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
func (api *API) handleParameterWebsocket(rw http.ResponseWriter, r *http.Request, render previewFunction) { | |
func (api *API) handleParameterWebsocket(rw http.ResponseWriter, r *http.Request, preview previewFunction) { |
still think we should call it preview, especially since that's what you named the type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will collide with the package name 😢
9f3529a
to
a6ce197
Compare
a6ce197
to
df65b92
Compare
Existing template versions do not have the metadata (modules + plan) in the db. So revert to using static parameter information from the original template import.
This data will still be served over the websocket.
TODO
Improve the error message when using static params.