feat(contracts/solve): most recent request per status #2675
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
corverroos
approved these changes
Dec 11, 2024
Zodomo
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added
getLatestRequestByStatus(status), which retrieves the most recent request to be set to a particular status. I also replaced thedeployedAtArbitrum branch handling with something much more robust.I attempted to add
getRequestUpdateHistory(id), which would return the timestamp history for all status updates a request has undergone. Despite this not altering the request and fulfillment flows, it broke the e2e tests, so this has been excluded for now.issue: #2679