Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#AutoResolveMissingInputs Krystex should auto-resolve inputs of dependencies for which resolvers are missing in a kryon. #Krystex #223

Closed
RamAnvesh opened this issue Feb 10, 2024 · 0 comments · Fixed by #327
Labels
good first issue Good for newcomers ready for dev size: s Small change
Milestone

Comments

@RamAnvesh
Copy link
Collaborator

RamAnvesh commented 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 not 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.

@RamAnvesh RamAnvesh added good first issue Good for newcomers size: s Small change ready for dev labels Feb 10, 2024
@RamAnvesh 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
@RamAnvesh RamAnvesh added this to the v9 milestone Feb 2, 2025
@RamAnvesh RamAnvesh linked a pull request Feb 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers ready for dev size: s Small change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant