You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the example share a very similar implemenetation of the core intereaction, servicing the messaging and keepting the shell-side view model up to date.
At the moment all the implementations couple the serialisation and view model management with other effect handling, but that can be improved.
We should design a common API surface for the Core and provide it as an "SDK" for each supported foreingn language.
A rough list of steps to achieve this:
Design a Core API which
Has update interface serialising the exported Events
Surfaces an "observable" (for the given UI toolkit) ViewModel instance, which is kept up to date
Services the Render effect and updates the view model
Allows for plugging in effect handlers for other effects (this probably requires a few POCs)
include an implementation in the exported foreign language code
move the doctor templates and examples to use the API
The text was updated successfully, but these errors were encountered:
All the example share a very similar implemenetation of the core intereaction, servicing the messaging and keepting the shell-side view model up to date.
At the moment all the implementations couple the serialisation and view model management with other effect handling, but that can be improved.
We should design a common API surface for the Core and provide it as an "SDK" for each supported foreingn language.
A rough list of steps to achieve this:
update
interface serialising the exportedEvent
sViewModel
instance, which is kept up to dateRender
effect and updates the view modelThe text was updated successfully, but these errors were encountered: