DcxIssuer Custom Handlers

[bnonni]

State

• DCX server allows devs to define custom handlers that truncate the prebuilt ones
• The order of execution is locked and devs must conform to the prebuilt order and handler arg/return structure

Goal

• Provide devs with pre-built handlers for running the issuer "out-of-the-box"
• Design and implement a way to easily have the pre-built and any custom handlers provided work together

Ideas

• some sort of JSON schema with different numbered priorities
• 0 to n: handlers execute in a monotonically increasing order

User Stories

• as a dev I want to
  • use all prebuilt in sequential order: p(1...4) && c(0)
  • use no prebuilt and custom in sequential order or not: p(0) && c(N...N)
  • use all prebuilt and custom in sequential order or not: p(N...N) && c(N...N)
  • use some prebuilt and custom in sequential order or not: p{N...N} && c(N...N)
  • decide when to turn on/off any combination of prebuilt and custom handlers defined