ui: Remove writable
usage from policy and use the request instead
#6934
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.
A recent change to the backend (#6874) meant that if you sent any data in the HTTP body that wasn't needed the backend would return an error.
In #6917 we changed the HTTP requests that weren't already using our
writable
functionality to remove data from the HTTP request that wasn't needed.writable
was used before we rewrite our data to achieve this, but our new data layer makes it much easier to see what is being sent to the server as it doesn't spread the information for the HTTP request over multiple files.This PR remove
writable
usage frompolicy
and continues to clean uptoken
and moves them to use our new data layer approach.We can't quite delete
writable
yet as in this branchintentions
still use it, but in #6639 we switched intentions to use our new approach also while we were there. Once #6639 and this PR are merged we can add another PR to completely removewritable
😁