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
Data Flows: cannot edit an operation #13702
Comments
Workaround would be to refresh when you are in editing screen. rec.mov |
I'm not able to reproduce this locally under the dev build, lemme try a prod instance |
Can confirm. This only happens in the prod build 🤦🏻 |
|
I got in edge :) Versie 101.0.1210.53 (Officiële build) (arm64) |
Ah yeah I edited the trigger, not the operation 👍🏻 |
Maybe timing thing between route/url update and opening the dialog/drawer. Dev build slower? |
I think these refs aren't correctly starting on the values of the prop due to some timing issue. The drawer should only be rendered if the prop exists, but for some reason there's a small discrepancy in timing between prod and dev of when the prop exists (I think) directus/app/src/modules/settings/routes/flows/components/operation-detail.vue Lines 99 to 102 in 6e87d8a
|
* Use immediate watcher instead of prop based ref default val Fixes #13702 * Make it happy * I'll be damned, it wasn't my stupidity after all
Thanks! I can confirm it works now! |
Describe the Bug
Hi,
first of all - long awaited feature with DataFlows - awesome!
But, once the flow is created, and an operation is added, it looks like, we cannot edit the operation, but we can replace it entirely i.e. Log in to console cannot be updated, after clicking Edit icon, the dialog with list of operations appears.
To Reproduce
Log in to console
and save itLog in to console
operation - the list of operations appears, not the operation itselfErrors Shown
None
What version of Directus are you using?
9.12.0
What version of Node.js are you using?
Docker
What database are you using?
Docker
What browser are you using?
Safari
How are you deploying Directus?
Docker
The text was updated successfully, but these errors were encountered: