-
Notifications
You must be signed in to change notification settings - Fork 75
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
Report with links #63
Comments
it might make sense to point these to the fast ruby repo as they are the source of truth for those issues. |
@dukaev would you wanna take a stab at this? If not, i'd close it. |
@DamirSvrtan yes. I'll do it within a week. |
In the first version, it will be possible to do it quickly. EXPLANATIONS = {
first: 'some warn [some_url.com]',
second: {
info: 'some warn',
link: 'some_url.com'
}
} @DamirSvrtan what do you think is the most suitable choice? |
Hi @dukaev 👋 I am sorry, I am not completely clear on your suggestion. Is your first suggestion to do it like this:
And the second one like this:
What do you think is the benefit of the first approach and what of the second one? Would you link out all the reports to https://github.com/JuanitoFatas/fast-ruby ? |
Hello @DamirSvrtan 🙂 In the first approach, In the second Yes. Links to JuanitoFatas/fast-ruby. Like https://github.com/JuanitoFatas/fast-ruby#hash-vs-openstruct-creation-code |
Hey Dukaev, let's go with the second solution (or something similar) where it's easy to grab the key of the offense or the link of the offense without additional parsing. |
👋 @DamirSvrtan. Added PR #78 |
Report with links will be more informative.
The text was updated successfully, but these errors were encountered: