AF-176: Hashes #96
Merged
AF-176: Hashes #96
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
SonarCloud Quality Gate failed.
|
Merged
mikecarenzo
approved these changes
Aug 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should be merged after #98 and #97
Hashes need to be published as objects with specific naming conventions for hash type.
Biggest change was that Hashes format is:
Hashes needs to be published as one single Object so a new method had to be created since
mergeBasicListPropertyexports only a single value and Hashes can contain multiple.This was breaking the build process because of no backwards compatibility for older .AFB files, this should produce warnings to tell users that they need to update their flows (attached to each Hash-having object that throws a warning)