tloncorp/landscape
1
1
Fork 0
mirror of https://github.com/tloncorp/landscape.git synced 2024-12-18 06:11:37 +03:00
Code Issues Packages Projects Releases Wiki Activity
207b31ce7e
landscape/desk/ted/save-summary.hoon

72 lines
2.0 KiB
Plaintext
Raw Normal View History

bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
:: -save-summary: unpack growl summary, store in mailchimp merge fields
::
:: crashes on failure. on success, produces the result message from the
:: -mailchimp-update-merge-fields thread.
::
bark: remove /sur/hark dependency from thread The "save summary" thread still had hark flagged as one of its dependencies, but doesn't actually use that for anything anymore. Here we simply remove the import.
2023-07-28 21:34:41 +03:00
/- spider
bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
/+ *strandio
=, strand=strand:spider
=, dejs:format
^- thread:spider
|= arg=vase
=/ m (strand ,vase)
^- form:m
=/ arg-mold
$: tlon-api-key=cord
bark: store mailchimp list-id in bark Alongside the mailchimp api key, we now store the list-id for the contacts lists which we're updating.
2023-07-19 00:31:30 +03:00
mailchimp=[key=cord list-id=cord]
bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
=ship
::
$= summary
bark: stop handling old summary response types Growl isn't actually live on any ships yet, so we do not need to account for this case.
2023-07-14 20:30:58 +03:00
$% [%life [sen=@ud rec=@ud gro=@t] [dms=@ud etc=@ud group=@t chat=@t]]
bark: clear bark data on-opt-out We shouldn't leave stale data in the mailchimp database, but rather wipe any data we've collected for users that are explicitly opting out.
2023-10-05 11:24:31 +03:00
[%wipe ~]
bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
==
==
=/ args !<([~ arg-mold] arg)
;< ~ bind:m
%- send-raw-card
:* %pass /check-email/(scot %p ship.args)
%arvo %k %fard
threads: reference correct desk
2023-08-15 01:27:34 +03:00
%landscape %hosting-email %noun
bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
!>(`[(trip tlon-api-key.args) ship.args])
==
;< [mire=wire mine=sign-arvo] bind:m take-sign-arvo
?> ?=([%check-email @ *] mire)
?> =(i.t.mire (scot %p ship.args))
?> ?=([%khan %arow %.y %noun *] mine)
::
=/ [%khan %arow %.y %noun vs=vase] mine
=+ !<(mail=(unit cord) vs)
bark: don't crash on no-mail summary saving Instead, give a %no-mail response message. It's not entirely unexpected to encounter ships that don't have a hosting account email address associated with them, so it shouldn't be a reason to crash. The crash is particularly problematic because as of the previous commits, we now actually show the trace of thread crashes.
2023-07-28 22:19:46 +03:00
?~ mail
(pure:m !>('no-mail'))
bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
;< ~ bind:m
%- send-raw-card
:* %pass /update-merge-fields/(scot %p ship.args)
%arvo %k %fard
threads: reference correct desk
2023-08-15 01:27:34 +03:00
%landscape %mailchimp-update-merge-fields %noun
bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
=; vars=(map @t json)
bark: store mailchimp list-id in bark Alongside the mailchimp api key, we now store the list-id for the contacts lists which we're updating.
2023-07-19 00:31:30 +03:00
!>(`[mailchimp.args u.mail vars])
bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
%- ~(gas by *(map @t json))
bark: clear bark data on-opt-out We shouldn't leave stale data in the mailchimp database, but rather wipe any data we've collected for users that are explicitly opting out.
2023-10-05 11:24:31 +03:00
=? summary.args ?=(%wipe -.summary.args)
[%life [0 0 ''] [0 0 '' '']]
?> ?=(%life -.summary.args)
bark: fix compilation error in merge fields thread We had removed the %hark case, but not the codepaths dealing with it.
2023-07-19 00:29:18 +03:00
=, summary.args
:~ ['MSGS_SENT' (numb:enjs:format sen)]
['MSGS_RECD' (numb:enjs:format rec)]
['GROUP_SENT' s+gro]
::
['UNREAD_DMS' (numb:enjs:format dms)]
['UNREAD_MSG' (numb:enjs:format etc)]
['GROUP_NAME' s+group]
['CHNL_NAME' s+chat]
bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
==
==
;< [wimp=wire simp=sign-arvo] bind:m take-sign-arvo
?> ?=([%update-merge-fields @ *] wimp)
?> =(i.t.wimp (scot %p ship.args))
?> ?=([%khan %arow %.y %noun *] simp)
::
=/ [%khan %arow %.y %noun vs=vase] simp
=+ !<([gud=? msg=@t] vs)
bark: small tweaks to threads The json serialization logic hadn't been updated correctly. We leave a better comment for easier reference. And we want more details to look at in the case something errors out.
2023-10-04 12:00:33 +03:00
?. gud ~|([ship=ship.args mail=u.mail msg] !!)
bark: accept new-style summaries And use the -save-summary thread to add the received details to our mailchimp contact database.
2023-07-14 19:04:23 +03:00
(pure:m !>(msg))
Reference in New Issue Copy Permalink