List view
The current “contact code” is currently both exposed to API consumer while simultaneously reaching all the way down into the bowels of the core message generation code in what is a kinda shocking top to bottom abstraction violation. Unfortunately this has resulted in years of existing library users deploying the same general approach you are currently taking to solve all sorts of contact related issues while simultaneously preventing some updates to the library even down at very bottom of the code stack without potentially breaking peoples applications in unexpected and difficult to fix ways. My thinking is once the library has been unburdened from the legacy API code (and the concern around breaking years of who know what contact hacking) we can update the core to “fix it right” while also providing everyone a route forward to the new API using a hopefully healthy abstraction.
No due date•4/5 issues closed