Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fix: add target type to the RMG012 diagnostic #310

Merged
merged 1 commit into from
Apr 12, 2023

Conversation

toddlucas
Copy link
Contributor

RMG023 was also updated to include the target type, due to the way the message is invoked alongside RMG012. The message format of RMG012 was updated to follow the format of RMG020.

This relates to #68

Copy link
Contributor

@latonz latonz left a comment

Choose a reason for hiding this comment

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

Thank you for your contribution 😊 Displaying the target type in the message of these diagnostics definitely makes sense!

RMG023 was also updated to include the target type, due to the way
the message is invoked alongside RMG012. The message format of RMG012
was updated to follow the format of RMG020.
@latonz latonz force-pushed the add-target-to-rmg012 branch from 4df144f to 001df7c Compare April 12, 2023 15:26
@latonz latonz enabled auto-merge (squash) April 12, 2023 15:27
@latonz latonz merged commit c092049 into riok:main Apr 12, 2023
@github-actions
Copy link

🎉 This PR is included in version 2.8.0-next.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants