-
Notifications
You must be signed in to change notification settings - Fork 2
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: add more validation to resource.router and add test cases #725
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Datadog ReportBranch report: ✅ 0 Failed, 129 Passed, 23 Skipped, 25.76s Total Time |
This PR breaks frontend for now since frontend calls the |
expect(result).toMatchObject(expected) | ||
}) | ||
|
||
it.skip("should throw 403 if user does not have write access to destination resource", async () => {}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we might need 1 more (skipped) test case: admin can move folders/pages from anywhere to root
it.skip("should throw 403 if user does not have read access to the resource", async () => {}) | ||
}) | ||
|
||
describe("delete", () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need a test case checking that the user cannot delete the root page
f69ee9e
to
c768018
Compare
3491a2d
to
420cf2e
Compare
420cf2e
to
d81f89e
Compare
d81f89e
to
dcfaa42
Compare
Merge activity
|
dcfaa42
to
b03df30
Compare
Second part of the PR. This PR adds tests for
resource.router
Blocked by #729