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
Some times some kryons don't resolve all the inputs of a dependency.
This is possible, for example, in the following scenario:
Let's say vajram A depends on vajram B, and vajram B has a single mandatory input.
This graph is built and deployed to production.
At a later point in time, the author of vajram B chooses to add a new optional input to vajram B. This should be a backward compatible change which should need Vajram A's author to update its code.
In this scenario, when vajram B is deployed to the runtime, the Krystex runtime should automatically resolve the the new optional input to Errable.empty().
This feature allows vajrams to evolve independently by adding new optional inputs in a backward compatible way.
The text was updated successfully, but these errors were encountered:
RamAnvesh
changed the title
#AutoResolveMissingInputs Krystex should auto-resolve inputs of dependencies for which resolvers are missing in a kryon
#AutoResolveMissingInputs Krystex should auto-resolve inputs of dependencies for which resolvers are missing in a kryon. #Krystex
Feb 10, 2024
Some times some kryons don't resolve all the inputs of a dependency.
This is possible, for example, in the following scenario:
Let's say vajram A depends on vajram B, and vajram B has a single mandatory input.
This graph is built and deployed to production.
At a later point in time, the author of vajram B chooses to add a new optional input to vajram B. This should be a backward compatible change which should need Vajram A's author to update its code.
In this scenario, when vajram B is deployed to the runtime, the Krystex runtime should automatically resolve the the new optional input to
Errable.empty()
.This feature allows vajrams to evolve independently by adding new optional inputs in a backward compatible way.
The text was updated successfully, but these errors were encountered: