String
Scheduling for {timestamp, date, ::MMMMd} at {timestamp, time, short}
Experiments
0The code that reads it uses no experiments, or so many that none of them stands out.
How we know: the 1 file reading it
0546a91e50430061.jsreads 31 strings · uses 1 experiment
Written next to it
Strings are stored in the order they were written, so neighbours usually belong to the same feature.
- Set Schedule
iQ1SwX - Message scheduled for {timestamp, date, long} at {timestamp, time, short}
CvHu/j - Successfully canceled the message.
JF/LWn - Scheduled message updated
MXsMRk - Message sent.
BHCm/d - Scheduling message for {timestamp, date, ::MMMMd} at {timestamp, time, short}
MQcRX/ - Scheduling for {timestamp, date, ::MMMMd} at {timestamp, time, short}
ZN3tIx - Scheduled time is too far away
Nt0tz7 - Scheduled time is too soon
w/fgvh - Scheduled Messages
SZVs3K - Today at 1:00pm
qT6LjY - Today at 9:00am
qINKo/ - Tomorrow at 1:00pm
EMRZyS