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
Of these, for remote languages we probably just need
pluginType (which could be e.g. "remote-language", "remote-kernel", "remote-evaluation" or something else probably including the word "remote"),
languageId, and
displayName
But surely we'll need to add other fields to handle remote kernels.
@jezdez you're closest to this at the moment, what other info will a language plugin need to define in order to be routed and handled correctly by iodide (obviously we don't need to think of everything, but if we know of things that we'll need for sure, we can add them)?
i think that as soon as we have an initial set of fields, me or @mdboom could do a quick PR to add the machinery for loading remote language kernel plugins pretty easily. (for the time being, we could set the evaluation to be a no-op in the case of a remote-eval)
The text was updated successfully, but these errors were encountered:
the current schema for language plugins is:
Of these, for remote languages we probably just need
But surely we'll need to add other fields to handle remote kernels.
@jezdez you're closest to this at the moment, what other info will a language plugin need to define in order to be routed and handled correctly by iodide (obviously we don't need to think of everything, but if we know of things that we'll need for sure, we can add them)?
i think that as soon as we have an initial set of fields, me or @mdboom could do a quick PR to add the machinery for loading remote language kernel plugins pretty easily. (for the time being, we could set the evaluation to be a no-op in the case of a remote-eval)
The text was updated successfully, but these errors were encountered: