We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Execute button on the deployments tab will show the body data in Advance Settings if you added data for execution previously.
Execute
body
This behaviour is missing in the Advance Settings if the Execute button is clicked in the Executions tab.
Executions
Consistent data in the Advance Settings when trying to execute a function from the Console.
Body data exists in Deployment tab, not in Executions tab.
Version 1.4.x
Linux
Appwrite 1.4.5.
1.4.5
The text was updated successfully, but these errors were encountered:
@ItzNotABug, thanks for raising this! 馃檹馃徏 I just tried this and it looks like the data will show in whichever modal you input in last...
That said, I think we typically clear the data after executing so if anything, we might update it to make sure to clear the data after submission.
Sorry, something went wrong.
@stnguyen90 Hmm, makes sense to clear the data post submission.
stnguyen90
No branches or pull requests
馃憻 Reproduction steps
The
Execute
button on the deployments tab will show thebody
data in Advance Settings if you added data for execution previously.This behaviour is missing in the Advance Settings if the
Execute
button is clicked in theExecutions
tab.馃憤 Expected behavior
Consistent data in the Advance Settings when trying to execute a function from the Console.
馃憥 Actual Behavior
Body data exists in Deployment tab, not in Executions tab.
馃幉 Appwrite version
Version 1.4.x
馃捇 Operating system
Linux
馃П Your Environment
Appwrite
1.4.5
.馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: