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

Fix bug with generated delete actions #74

Merged
merged 4 commits into from
Dec 9, 2024
Merged

Conversation

pipex
Copy link
Collaborator

@pipex pipex commented Dec 6, 2024

Tasks for delete operations can skip the deletion of the property being referenced because Mahler performs the delete operation after the successful execution of the given action. This fixes a bug where the deletion was happening too early before the inner function returned

Change-type: patch

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@flowzone-app flowzone-app bot enabled auto-merge December 6, 2024 20:24
@pipex
Copy link
Collaborator Author

pipex commented Dec 6, 2024

I self-certify!

pipex added 4 commits December 6, 2024 18:05
Tasks for delete operations can skip the deletion of the property being
referenced because Mahler performs the delete operation after the
successful execution of the given action. This fixes a bug where the
deletion was happening too early before the inner function returned

Change-type: patch
The calculation would before also consider library defaults, but either
the defaults would not contribute to differentiating the id or in some
cases, where the functions are overriden, it would erroneously generate
the same id for two tasks that are different.

Change-type: patch
Since making the `system` parameter readonly, the task definitions on
the blocks tests were invalid.
Hopefully for the last time since fixing the task id calculation
@flowzone-app flowzone-app bot merged commit 7d89563 into main Dec 9, 2024
55 checks passed
@flowzone-app flowzone-app bot deleted the delete-await-bug branch December 9, 2024 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants