~singpolyma/sgx-jmp

ref: 4f26f5f84be11e7cc4eb94c0f7bd4a20e11c7775 sgx-jmp/lib/bwmsgsv2_repo.rb -rw-r--r-- 2.2 KiB
Set location when moving to v2 SIP

From configure calls as well as from reset sip account.
Merge branch 'rubocop'

* rubocop:
  Additional fixes for rubocop 1.10.1
  Switch to rubocop 0.89.1
Additional fixes for rubocop 1.10.1

This is the default rubocop in Guix.
Merge branch 'configure-calls-v2'

* configure-calls-v2:
  New configure calls command
  Move more persistence into the repo layer
  Easy DSL for adding XEP-0122 validation to fields
  CustomerFwd uses ValueSemantics, translates old XMPP-SIP URI
Move more persistence into the repo layer

BackendSGX shouldn't touch Redis, instead get one of the repos to save the data
we want saved wherever that repo saves it (in this case, those same Redis keys).
CustomerFwd uses ValueSemantics, translates old XMPP-SIP URI

More of the original data is kept now, so this object could be used for putting
to persistence as well as for loading from it.
Move CustomerFwd behind Customer

All the previously-lazy BackendSgx data is now either all loaded or all not
loaded by swapping the sgx_repo used by your CustomerRepo instance.  When not
loaded the fields are filled with bottom values that explode when used.  When
loaded the values are present in RAM and not promises at all.  Most code paths
do not need any of the data, a few need most of it, so this seems like a good
trade-off.  Most code using this object will simply never touch those fields or
care about how they are loaded, etc.

Of course, most of this data isn't even SGX related and should move out of here,
but that would take a data model refactor/migration on the catapult_* schema.