Currently, the messages being sent across the multiple extension services (Data Editor UI, Data Editor Client instance, and the DFDL Debug Session) have no strict types or content structure. This becomes problematic when attempting to implement functionality in relation to a specific event and its content because there is only runtime raw JS object resolution.
These messages can be templated and stored for compile type resolution for a more orthogonal development structure.
Currently, the messages being sent across the multiple extension services (Data Editor UI, Data Editor Client instance, and the DFDL Debug Session) have no strict types or content structure. This becomes problematic when attempting to implement functionality in relation to a specific event and its content because there is only runtime raw JS object resolution.
These messages can be templated and stored for compile type resolution for a more orthogonal development structure.