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.
Please check second sorting demand
Finding active users is not the main problem in beta process. But I agree with you, I've discontinued kata authoring myself because I'm fed up.
Hi, nice series of katas. Learned a lot by solving your katas. Thank you!
Hello, quick question about one of the hard coded test examples.
DB[:campaign_sends].multi_insert([
current send - baseline
{ user_id: 1, sent_at: '2023-01-08 08:00:00', campaign_id: 'new_year', channel: 'email' },
exactly 7 days ago --> should count as prior touch
{ user_id: 1, sent_at: '2023-01-01 08:00:00', campaign_id: 'new_year', channel: 'sms' },
7 days + 1 second after (2023-01-01 08:00:01) --> too late, outside the window
{ user_id: 1, sent_at: '2023-01-01 08:00:01', campaign_id: 'new_year', channel: 'push' },
same moment as current send --> does not count as prior
{ user_id: 1, sent_at: '2023-01-08 08:00:00', campaign_id: 'new_year', channel: 'sms' },
valid message 1 hour before --> valid prior
{ user_id: 1, sent_at: '2023-01-08 07:00:00', campaign_id: 'new_year', channel: 'push' }
])
In the "Check Windows" section of the tests your third row example { user_id: 1, sent_at: '2023-01-01 08:00:01', campaign_id: 'new_year', channel: 'push' }, says above it "7 days + 1 second after" and that it shouldn't be counted as a prior but isn't '2023-01-01 08:00:01' actually 6 days, 23 hours, 59 minutes and 59 seconds before the baseline which is '2023-01-08 08:00:00'?
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
Hi! 💛💙
Right now I’m feeling inspired to create some more challenging SQL katas (around 4–5 kyu), but as you know, it’s often hard to find enough active reviewers on Codewars to help move them out of beta.
If you ever have a time to solve them and leave some feedback, I'd be truly grateful 🙏
Why even include 2023 year condition, to check if one can write where clause?
This is indeed my longest solution across all my solved kata. I ended up with 3x the number of lines of my next largest solution (for another 1 kyu kata)!
Take into account there is a fairly complete input language here; the code for the parser alone is about the same size as that next largest solution. And outputting BF, even with well-factored code, tends to require some verbosity.
I might pick this up at some point. I already started on a Rust version, your version could be helpful in accellerating the process.
I have proofread the description and updated it a bit for spelling, grammar and tone.
I have also edited all the translations to fix typos and a small issue with the End before beginning a block test (adding a backslash to the single quote in the
msg
statement).Yes, your example is invalid code and should throw an error.
A
call
uses the variablevarx
andvarx
has not been defined at the time of the call.I note that this scenario is not actually being tested.
Expurple's example is also invalid, beause there is no
changeA
variable defined.proc
parameters are not global definitions.Marking as answered.
This has long since been resolved.
This has long since been resolved (current versions are 2.14 and 3.3).
Loading more items...