fix: remove the erroneous warn function #44
Merged
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.
Description of the change
With recent refactoring efforts on the transformations action code to improve the code coverage etc, we added a warning log using actions/core with convention as
core.warn()
. This was added in the release v1.1.1. Changes in the PR:This was a breaking change as the fn doesn't exist
. The test covering the codepath also wasn't present at that time which resulted in the change going in undetected. This change fixes it by removing the warn log altogether.We also have added tests now for covering some of the missing paths in the action code.
Type of change
Related issues
Checklists
Development
Code review