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.

Sign up for GitHub

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

Jump to bottom

Use LLMs to infer arg names of generated configurations #2652

Closed
tusharmath opened this issue Aug 11, 2024 · 12 comments · May be fixed by #2787
Closed

Use LLMs to infer arg names of generated configurations #2652

tusharmath opened this issue Aug 11, 2024 · 12 comments · May be fixed by #2787
Labels
💎 Bounty state: inactive No current action needed/possible; issue fixed, out of scope, or superseded.

Comments

@tusharmath
Copy link
Contributor

tusharmath commented Aug 11, 2024 •
edited
Loading

Tailcall uses the power of AI to auto-generate configurations. This feature is primarily used to identify the name of the type currently and works reliably well.

Before

type Query {
  f1(p1: Int): [T1] @http(path: "/users/{{args.p1}}")
}

After infer_type_names: true

type Query {
  f1(p1: Int): [User] @http(path: "/users{{args.p1}}")
}

After infer_arg_names: true

type Query {
  f1(id: Int): [User] @http(path: "/users{{args.id}}")
}

Technical Requirements

  • NOTE: Ensure the mustache templates are also updated.
  • NOTE: the fieldName that is a required field should be made optional and used only if provided.
  • Try to produce minimal diff and abstract out common parts out of infer_type_name.rs and the new infer_arg_name.rs.
  • Add snapshot tests for the generated configurations

Additional Links
@tusharmath
Copy link
Contributor Author

/bounty 65$

@algora-pbc Algora PBC
Copy link

algora-pbc bot commented Aug 11, 2024 •
edited
Loading

## 💎 $65 bounty • Tailcall Inc.

### Steps to solve:
1. Start working: Comment /attempt #2652 with your implementation plan
2. Submit work: Create a pull request including /claim #2652 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.
💵 More about our bounty program.

Attempt Started (GMT+0) Solution
🔴 @ssddOnTop Aug 11, 2024, 8:18:18 AM WIP
🔴 @mobley-trent Aug 13, 2024, 6:37:31 AM WIP
🟢 @beelchester Aug 14, 2024, 5:41:29 AM #2687
🟢 @laststylebender14 #2787

@ssddOnTop
Copy link
Member

ssddOnTop commented Aug 11, 2024 •
edited by algora-pbc bot
Loading

/attempt 2652

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

@algora-pbc Algora PBC
Copy link

algora-pbc bot commented Aug 12, 2024

@ssddOnTop: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏

@mobley-trent
Copy link
Contributor

mobley-trent commented Aug 13, 2024 •
edited by algora-pbc bot
Loading

/attempt #2652

Algora profile Completed bounties Tech Active attempts Options
@mobley-trent    2 tailcallhq bounties
+ 7 bounties from 4 projects
Python, Rust,
Jupyter Notebook
Cancel attempt

@algora-pbc Algora PBC
Copy link

algora-pbc bot commented Aug 13, 2024

Note

The user @ssddOnTop is already attempting to complete issue #2652 and claim the bounty. We recommend checking in on @ssddOnTop's progress, and potentially collaborating, before starting a new solution.

@beelchester
Copy link
Contributor

beelchester commented Aug 14, 2024 •
edited by algora-pbc bot
Loading

/attempt #2652

Algora profile Completed bounties Tech Active attempts Options
@beelchester 8 tailcallhq bounties
Rust, TypeScript,
CSS & more
Cancel attempt

@algora-pbc Algora PBC
Copy link

algora-pbc bot commented Aug 14, 2024

Note

The user @mobley-trent is already attempting to complete issue #2652 and claim the bounty. We recommend checking in on @mobley-trent's progress, and potentially collaborating, before starting a new solution.

@beelchester beelchester mentioned this issue Aug 14, 2024
Closed
@algora-pbc Algora PBC
Copy link

algora-pbc bot commented Aug 14, 2024

@mobley-trent: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏

@laststylebender14 laststylebender14 mentioned this issue Sep 3, 2024
Open
6 tasks
@algora-pbc Algora PBC
Copy link

algora-pbc bot commented Sep 3, 2024

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

@github-actions GitHub Actions
Copy link

github-actions bot commented Oct 9, 2024

Action required: Issue inactive for 30 days.
Status update or closure in 7 days.

@github-actions github-actions bot added the state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. label Oct 9, 2024
@github-actions GitHub Actions
Copy link

Issue closed after 7 days of inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
💎 Bounty state: inactive No current action needed/possible; issue fixed, out of scope, or superseded.
Projects
None yet
Milestone
No milestone
4 participants
@tusharmath @ssddOnTop @mobley-trent @beelchester