Closed tusharmath closed 2 weeks ago
/bounty 100$
## 💎 $100 bounty • Tailcall Inc.
### Steps to solve:
1. Start working: Comment
/attempt #1698
with your implementation plan2. Submit work: Create a pull request including
/claim #1698
in the PR body to claim the bounty3. 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 |
---|---|---|
🔴 @timburrows | Apr 13, 2024, 3:32:38 AM | WIP |
🔴 @emekaokoli19 | Apr 20, 2024, 3:06:55 AM | WIP |
/attempt #1698
@timburrows: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏
The bounty is up for grabs! Everyone is welcome to /attempt #1698
🙌
I'm still looking into this but I haven't determined a good way to maintain Pos data on each of the fields without a lot of otherwise unused members on each struct. I was considering that if the only use case was for tracing, keeping a key value pair might suffice?
/attempt #1698
Action required: Issue inactive for 30 days. Status update or closure in 7 days.
Issue closed after 7 days of inactivity.
Action required: Issue inactive for 30 days. Status update or closure in 7 days.
Issue closed after 7 days of inactivity.
Currently
Config
type doesn't hold any position information in its fields. This makes it extremely difficult to debug and attach meaningful traces. In this issue, we want to insert tracing information in the config. That way we could see better errors:Current
Expected
Going forward we would be able to extract a piece of text from the source file and display it on the CLI with swiggly lines under it.
Technical Requirements
Add a new type called
Pos
for each field inConfig
. This field is essentially transparent to the serializer/deserializermerge_right
onPos
in such a way that position information is correctly merged. Ensure information is stored in Pos from wherever the data is read from.