-
Notifications
You must be signed in to change notification settings - Fork 569
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
Disable endowment:long-running
in stable
#1103
Comments
Do we just want to remove it in its entirety until we come up with a new solution? Otherwise, we will have to maintain it even though it isn't in use. |
We agreed in a prioritization call to disable for now in stable and remove all together once we have a replacement API. |
Use the new |
Closing for now since it is technically fenced correctly, but we should remember to keep the fencing as-is when we remove the Flask fencing. |
#945 requires rethinking a new API to allow useful Snap use-cases that used this behaviour before.
It's important to support those case, but we also want to avoid scope creep for v1.0.0 release of Snaps.
Outcome
endowment:long-running
in stable altogether and post a deprecation warning in FlaskThe text was updated successfully, but these errors were encountered: