-
Notifications
You must be signed in to change notification settings - Fork 39
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
Fetch All Closed Events - Cairo Contract #113
Comments
Could I take a shot at this? |
Application for Fetching All Closed Events - Cairo ContractHi @mubarak23, I am interested in implementing this feature to fetch all closed events in the Implementation Plan
ETAI estimate completing this within 12 hours, ensuring proper functionality and comprehensive test coverage. Looking forward to your approval! 🚀 Best, |
Can I jump on this task? |
Is it okay if I tackle this? |
I’d love to work on this task. |
Hi, I am proficient Blockchain developer expert in Cairo , Rust and Solidity and also in web development. |
Hi, I'm a Cairo Smart Contract Developer, and I'll love to carry this out |
May I take this issue on? |
I'd like to handle this task. |
Can I jump on this task? |
I will fetch all closed eventsI am from Starknet Winter Hackathon I have great experience with Cairo, and am familiar with this codebase. I would love to work on this, fetch the closed events and write a detailed test. ETA: 8 hours prompt. |
Can I take care of this issue? |
I’d like to create the smart contract function to fetch all closed events, returning an array of EventDetails. This includes adding the interface function to IEvent.cairo, implementing it in chaineventts.cairo, and writing tests to ensure functionality and reliability. |
Can I take care of this issue? |
Hi there! 👋 I’m a software engineer and blockchain developer with experience in Cairo, Solidity, JavaScript, TypeScript, and Rust. I’m excited to make my first contribution on OnlyDust and would love to take on this issue! My approach To implement the fetch_all_closed_events function, I will first add the interface function fn fetch_all_closed_events(self: @TContractState) -> Array; to IEvent.cairo to define the expected behavior. Next, I will write the function logic inside the chaineventts.cairo contract. The function will iterate through all events using the event_counts variable, check if each event’s is_closed flag is true, and append closed events to an array to be returned. To ensure correctness, I will write comprehensive tests that cover scenarios such as no closed events, all events closed, and mixed open/closed events. This approach ensures the function meets the acceptance criteria and integrates seamlessly with the existing contract. |
Create a Smart Contract function that fetch All Closed Events, the function should return Array of EventDetails
Add the interface function inside IEvent.cairo
fn fetch_all_closed_events(self: @TContractState) -> Array<EventDetails>;
write your function inside chaineventts contract.
(event/chaineventts.cairo)
Acceptance criteria
Duration: 1 Day
The text was updated successfully, but these errors were encountered: