Skip to content
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

feat: the WF engine should resolves escaped variables - WF-53 #568

Conversation

FabienArcellier
Copy link
Collaborator

@FabienArcellier FabienArcellier commented Sep 23, 2024

  • feat: handle escape variable in exchange protocol
  • feat: handle escape variable in auto-completion
  • feat: state support dot variable

Peek 2024-10-07 10-10

@FabienArcellier FabienArcellier added the enhancement New feature or request label Sep 23, 2024
@@ -186,7 +195,7 @@ const showAutocomplete = () => {
const handleBlur = () => {
setTimeout(() => {
autocompleteOptions.value = [];
}, 100);
}, 300);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I encountered cases where the handler reaction was too fast. We may have to change this behavior in the future to have a flag to show or hide the autocompletion.

@FabienArcellier FabienArcellier self-assigned this Sep 24, 2024
@FabienArcellier FabienArcellier force-pushed the 513-the-wf-engine-should-resolves-escaped-variables branch from 6ce8c5a to 4f7988a Compare September 24, 2024 05:44
@FabienArcellier FabienArcellier changed the title feat: the WF engine should resolves escaped variables feat: the WF engine should resolves escaped variables - WF-53 Oct 3, 2024
@FabienArcellier FabienArcellier marked this pull request as ready for review October 7, 2024 07:54
@FabienArcellier FabienArcellier force-pushed the 513-the-wf-engine-should-resolves-escaped-variables branch from 4f7988a to aa72445 Compare October 7, 2024 07:55
* feat: handle escape variable in exchange protocol
* feat: handle escape variable in auto-completion
* feat: state support dot variable
@FabienArcellier FabienArcellier force-pushed the 513-the-wf-engine-should-resolves-escaped-variables branch from aa72445 to b855d8c Compare October 10, 2024 07:52
@ramedina86 ramedina86 merged commit d84100b into writer:dev Oct 11, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants