Resolve Ambiguous Types in Configuration Automatically

[amitksingh1490]

Issue Description:
Presently, when the same type is used in both the input and output sections of the configuration in our definitions.rs file

tailcall/src/blueprint/definitions.rs

Line 536 in dd2114d

} else if dbl_usage {

.
(ref: line 536), the Tailcall CLI throws an error.

To enhance the user experience we can infer this from the config, we can leverage the existing resolve_ambiguous_types function in the ConfigModule to automatically resolve this issue.

Requirements:

• The Tailcall CLI no longer throws errors when the same type is used in both the input and output sections of the configuration.
• Ambiguous type are automatically detected and resolved using the resolve_ambiguous_types function.
• Integration test for this using execution_spec should be added.

[tusharmath]

/bounty 150$

[algora-pbc]

💎 $150 bounty • Tailcall Inc.

Steps to solve:

1. Start working: Comment /attempt #1870 with your implementation plan
2. Submit work: Create a pull request including /claim #1870 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

🙏 Thank you for contributing to tailcallhq/tailcall!
🧐 Checkout our guidelines before you get started.

Attempt	Started (GMT+0)	Solution
🟢 @ssddOnTop	May 13, 2024, 6:29:32 AM	#2024

[ssddOnTop]

/attempt

Algora profile	Completed bounties	Tech	Active attempts	Options
@ssddOnTop	43 tailcallhq bounties	Rust, Java, C & more		Cancel attempt

[tusharmath]

Thanks @maks-ivanov sorry had to delete your AI Generated comment. It was causing more confusion and wasn't correct. Request you to not comment with AI-generated content in the future.

[algora-pbc]

💡 @ssddOnTop submitted a pull request that claims the bounty. You can visit your bounty board to reward.

[algora-pbc]

🎉🎈 @ssddOnTop has been awarded $150! 🎈🎊

• Share on socials
• Give feedback