You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Server Version: 2.0.10
CLI Version (for CLI related issue): 2.0.0-beta.1
Environment
Localhost (MacOS)
What is the expected behaviour?
After adding the session arguments to a tracked volatile function (tracked as mutation), it should simply work!
Keywords
functions, mutation, session argument
What is the current behaviour?
After adding the session arguments to a tracked volatile function (tracked as mutation), the metadata removes the exposed_as: mutation which turns it into a normal (tracked as a query) function. This can be fixed by manually changing the yaml file in the metadata so the bug is related to the UI console.
How to reproduce the issue?
Create a volatile function that gets a session argument and track it as a mutation
Set the session argument name
Watch as it changes to a query instead!
Any possible solutions?
Probably a simple bug in the console.
If the bug is confirmed, would you be willing to submit a PR?
Nope!
The text was updated successfully, but these errors were encountered:
Version Information
Server Version: 2.0.10
CLI Version (for CLI related issue): 2.0.0-beta.1
Environment
Localhost (MacOS)
What is the expected behaviour?
After adding the session arguments to a tracked volatile function (tracked as mutation), it should simply work!
Keywords
functions, mutation, session argument
What is the current behaviour?
After adding the session arguments to a tracked volatile function (tracked as mutation), the metadata removes the
exposed_as: mutation
which turns it into a normal (tracked as a query) function. This can be fixed by manually changing the yaml file in the metadata so the bug is related to the UI console.How to reproduce the issue?
Any possible solutions?
Probably a simple bug in the console.
If the bug is confirmed, would you be willing to submit a PR?
Nope!
The text was updated successfully, but these errors were encountered: