chore(angular-output-target): remove directivesUtilsFile #315
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 commit removes a parameter for the
angularOutputTarget()
method that was not accessed anywhere in the output generation code.Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build
) was run locally for affected output targetsnpm test
) were run locally and passednpm run prettier
) was run locally and passedPull request type
Please check the type of change your PR introduces:
What is the current behavior?
The
directivesUtilsFile
target method param was not accessed anywhere in the output code after it ran through the validation method.Issue URL: N/A
What is the new behavior?
The field is removed
Does this introduce a breaking change?
The field is not currently doing anything, so users will just need to remove it from the output target config if the Angular wrapper is used.
Other information