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

feat: pass ExecutionInput to getOrElse method #1918

Merged
merged 3 commits into from
Jan 25, 2024

Conversation

samuelAndalon
Copy link
Contributor

@samuelAndalon samuelAndalon commented Jan 25, 2024

📝 Description

trying to implement a distributed cache mechanism for parsed and validated operations, in the getOrElse method is where we would be setting the operation into an external cache, for that, we need access to the actual operation, which is included in the ExecutionInput.

No more changes are needed given that the action of storing the parsed and validated operation is potentially async, but we don't care about the result.

@tapaderster
Copy link
Member

can you please add a description with the reason for this?

@samuelAndalon samuelAndalon merged commit e6ab991 into master Jan 25, 2024
8 checks passed
@samuelAndalon samuelAndalon deleted the feat/execution-input-apq branch January 25, 2024 02:34
samuelAndalon added a commit that referenced this pull request Jan 25, 2024
### 📝 Description
trying to implement a distributed cache mechanism for parsed and
validated operations, in the `getOrElse` method is where we would be
setting the operation into an external cache, for that, we need access
to the actual operation, which is included in the `ExecutionInput`.

No more changes are needed given that the action of storing the parsed
and validated operation is potentially async, but we don't care about
the result.
samuelAndalon added a commit that referenced this pull request Jan 25, 2024
### 📝 Description
trying to implement a distributed cache mechanism for parsed and
validated operations, in the `getOrElse` method is where we would be
setting the operation into an external cache, for that, we need access
to the actual operation, which is included in the `ExecutionInput`.

No more changes are needed given that the action of storing the parsed
and validated operation is potentially async, but we don't care about
the result.

### 📝 Description


### 🔗 Related Issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants