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(api) restrict data manipulation operations on 'off' db with errors #4308

Merged
merged 3 commits into from
Feb 15, 2019

Conversation

bungle
Copy link
Member

@bungle bungle commented Feb 13, 2019

Summary

Here are the "features" and tests for reporting errors with off database strategy.

@bungle bungle requested a review from hishamhm February 13, 2019 19:11
@bungle bungle force-pushed the feat/dbless-restrict-endpoints branch from 1d07772 to 1bd6ff5 Compare February 13, 2019 19:12
@hishamhm hishamhm force-pushed the feat/dbless-cache branch 7 times, most recently from 3dcdfe6 to d8f3e6b Compare February 14, 2019 15:35
@bungle bungle force-pushed the feat/dbless-restrict-endpoints branch 2 times, most recently from 0c63b01 to 2a85815 Compare February 14, 2019 16:11
@hishamhm hishamhm force-pushed the feat/dbless-cache branch 2 times, most recently from fba1cdd to 5b00cc7 Compare February 14, 2019 19:21
@hishamhm hishamhm force-pushed the feat/dbless-restrict-endpoints branch from 2a85815 to ea8836a Compare February 14, 2019 19:46
@hishamhm hishamhm added this to the 1.1.0 milestone Feb 14, 2019
@hishamhm hishamhm force-pushed the feat/dbless-restrict-endpoints branch from ea8836a to b2cbec1 Compare February 14, 2019 19:54
@hishamhm hishamhm force-pushed the feat/dbless-restrict-endpoints branch from b2cbec1 to 05f6df9 Compare February 14, 2019 21:01
@bungle bungle added pr/ready This PR is considered ready and can be merged at anytime (given it received no subsequent changes) and removed pr/please review labels Feb 15, 2019
@hishamhm hishamhm merged commit 95bfe6a into feat/dbless-cache Feb 15, 2019
@hishamhm hishamhm deleted the feat/dbless-restrict-endpoints branch February 15, 2019 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/ready This PR is considered ready and can be merged at anytime (given it received no subsequent changes)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants