Move AACI and coerce logic to hz_aaci.erl #17
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "hz_aaci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now hz_aaci:erlang_to_fate and hz_aaci:fate_to_erlang are exposed functions that projects like SFP can use.
The loops that go through lists/maps/tuples/records/variants and convert their elements back and forth, are still made in the overloaded dispatchy way, but the function that used to be called 'coerce' is now more honest about its responsibilities.
I also removed the hz:prepare_aaci function, which converts an erlangy ACI into an erlangy AACI, and exposed it as hz_aaci:prepare_aaci instead. It seems like if you are handling ACI terms yourself, you're doing non-standard low-level stuff that shouldn't pollute and confuse hz.erl
Checkout
From your project repository, check out a new branch and test the changes.