Note though, that this only works when you're already using git for your dependency
I was trying to figure out why it wasn't working for me. This was probably the reason.
So if you just have gem 'rack', it just silently has no effect.
It seems like it should just work either way. Or at least give a warning/error if you try to use this config and it's not going to use that config!
Can't annotate on https://feedback.mailgun.com/forums/156243-feature-requests/suggestions/39905227-provide-meaningful-delivery-status-description-rat so posting here instead.
Anonymous commented · May 26, 2021 4:36 AM
Without your comment I'd never find the real issue, because I was only look at permanent failures. That error message is really misleading, hope they can fix this.
Kelly commented · December 30, 2020 2:35 AM
Yes we desperately need this too. Half of our recipients were soft bounced due to "Too old" but we could still send to them previously on other ESPs.
This was originally disallowed because #5907 was opened asking for different behavior in this situation that we didn't want to allow, and so we decided to make it a compiler error rather than have confusing behavior in that situation.
The console needs to be readable in development and to provide the best DX I have to design my libraries in ways that prevent these warnings. This results in design decisions that are detrimental to functionality and/or code readability/simplicity.
Indeed, if MoneySerializer was reloadable, starting with Rails 7 such initializer would raise a NameError.
We’ve enabled deprecation warnings by default when running specs. Making these warnings more visible to developers helps upgrading to newer Ruby versions.
wanted to surface to the user during SSR if the client-side call would likely fail due to cross-origin fetching, credentials, etc.
Mentioned here:
but I can't find it on my system
I should note that the issue with deletions being skipped has been fixed (the file-has-vanished errors were changed into warnings).
certainly I wouldn't want it to start telling me that I'm not catching these!
Get told in big red letters when the dependency changed and you need to check that your fix is still valid.
`Module ${a.id} may be unable to evaluate without ${b.id}, but is included first due to a cyclical dependency. Consider swapping the import statements in ${parent} to ensure correct ordering`
Since this issue seems to pop up periodically, it would be useful to turn this into a warning. It may not be elegant, but it prevents surprise blank screens due to a navigation error.
Not an actual fix.
It is showed as an error, but it is a warning as it doesn't break anything. I hate having warning/error in my console not coming from me. It is not justified as it's not bad practice imho