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
The second one was inspired by the first one.
And the first isn't completely compliant with the Eno architecture.
In theory, the Table driver should write some elements, call some functions and continue the process with the children of the input.
Those children will call some other drivers, etc....
When I wrote the functionnality, I could not manage to do that, so I use a function to directly get the elements I needed as children and do the treatment within the Table Driver.
Some functions on the DDI side are a little weird.
It will be an improvement to refactor that part.
The text was updated successfully, but these errors were encountered:
The second one was inspired by the first one.
And the first isn't completely compliant with the Eno architecture.
In theory, the Table driver should write some elements, call some functions and continue the process with the children of the input.
Those children will call some other drivers, etc....
When I wrote the functionnality, I could not manage to do that, so I use a function to directly get the elements I needed as children and do the treatment within the Table Driver.
Some functions on the DDI side are a little weird.
It will be an improvement to refactor that part.
The text was updated successfully, but these errors were encountered: