Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
oh, and as a suggestion: maybe we need more edge cases here, as it is quite hard to debug 30+ convert events within of 100+ rows
description says
but in the tests expected output for a random test seem to be sorted just by channel:
it's hard to figure out from description whether there could be several 'converted' events for the same user
description says
but it is not clear for me do you mean data in campaign_sends or in engagement_events or both, as that rows could have different timestamps in different fields
This comment is hidden because it contains spoiler information about the solution
maybe it would be useful to mention that applicant_ids should be ordered in the text as well
Thank you
From my perspective it's more a form of lazyness, like I don't want to write a lot and it's hard to keep in mind a lot of querries, so I try to make a shorter solution with less selects and joins. Also 'case when then' looks as an awkward construction for me so I try to avoid it as well.
Of course such tricks often is not a good thing in production code.
91
it would be better to show actual, expected and diff tables for the better user experience. You could look at the other kata that povide such an info. e.g. this one
This comment is hidden because it contains spoiler information about the solution
in JS message like
isn't very useful. I see the input but almost no information about expected answer.
That's in Random tests
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
thanks!
seems to work better now (anyway I fixed my solution before ;) )
in JS tests output is truncated like
so it is hard to debug
some names seem to be completely random, but there is some 'logic':
segments -> ss -> ß
result -> r
last -> l
Loading more items...