-
Notifications
You must be signed in to change notification settings - Fork 58
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
Fix for platformResultsPreMapper/concat problem #355
Conversation
I tried this out and it looks like it gets past the original error, but hits another.
Did I do something to break Babel? Additionally, this is an issue payload, but it's trying to hit the Is that related to this, or is something else going on? |
@jlengstorf can you clarify if this most recent error uses the |
@ashfurrow I tried it with and without Another error we started seeing: gatsbyjs/gatsby#7409 (comment) |
@ashfurrow I went ahead and rolled our installation back to avoid these bugs. The fix here gets around the original issue, but now we get:
No idea what's going on, so I guess I need to wait for @orta to get back before upgrading again. Thanks again for your help! |
OK, I know what the issue is about (WRT the mysterious PR request) - it's because the level of abstraction for Danger is only PRs the checks API is used on every request, but because when using danger on an issue we support communicating using Danger ( e.g. Once I get some time with a computer at home, I'll take a look. Things got a bit rough from thursday, so I'm not quite in a space to say when I can do it - likely this week/weekend |
@orta hey, no rush at all; I'll stop pinging you. So sorry for your loss. |
OK, I've taken a look and I think I've got it with #359 - the key is that nullfunc, we don't need it, just needed it to be totally falsy. I set myself up to also have a danger file running on issues for danger so it should be accounted for in general |
Nice! I'll pull down and test it on my end. |
Worked fine for me, thanks Orta: ashfurrow/test-repo#14 (comment) |
So it took looking at the Danger and Peril codebases side-by-side to realize that we've got a subtle type bug. The
Platform
type expects an optionalplatformResultsPreMapper
, but Peril was setting that attribute to be a function that returns an optional function. The fix was to move the tertiary expression outside of theplatform
const definition, to run that check before creating thePlatform
object (instead of running the check when theplatformResultsPreMapper
function is called, returning a function where pre-mapper results are expected to be returned).I've tested and verified this works: ashfurrow/test-repo#13
Fixes #351. Fixes ashfurrow/peril-settings#8.