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

Simplify app development with dedicated API for tasks not depending on volatile process state #25

Open
Viir opened this issue Apr 27, 2024 · 0 comments

Comments

@Viir
Copy link
Member

Viir commented Apr 27, 2024

So far, we always use volatile processes to run tasks integrating other software.
However, in many cases, we don't need the facilities to retain volatile process state beyond a single task. Examples are usages of elm-format and elm make in Elm Editor.

A dedicated API for a single task would simplify application developers' implementation. For example, this part should be simpler (And more complete, forwarding any errors that were not linked to RequestToVolatileProcess):

Err Platform.WebService.ProcessNotFound ->
( httpResponseInternalServerError
("Error: Volatile process '"
++ pendingTask.volatileProcessId
++ "' disappeared. Starting volatile process again... Please retry."
)
, Just pendingTask.volatileProcessId
)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant