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

Resolve Ambiguous Types in Configuration Automatically #1870

Closed
3 tasks
amitksingh1490 opened this issue May 6, 2024 · 6 comments · Fixed by #2024
Closed
3 tasks

Resolve Ambiguous Types in Configuration Automatically #1870

amitksingh1490 opened this issue May 6, 2024 · 6 comments · Fixed by #2024

Comments

@amitksingh1490
Copy link
Collaborator

amitksingh1490 commented May 6, 2024

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

} 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.
@tailcallhq tailcallhq deleted a comment from maks-ivanov May 13, 2024
@tusharmath
Copy link
Contributor

/bounty 150$

Copy link

algora-pbc bot commented May 13, 2024

💎 $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
Copy link
Member

ssddOnTop commented May 13, 2024

/attempt

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

@tusharmath
Copy link
Contributor

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.

Copy link

algora-pbc bot commented May 30, 2024

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

Copy link

algora-pbc bot commented May 31, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants