-
-
Notifications
You must be signed in to change notification settings - Fork 690
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
check_visibility can now take multiple permissions into account #1842
Conversation
Codecov ReportBase: 92.52% // Head: 92.54% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #1842 +/- ##
==========================================
+ Coverage 92.52% 92.54% +0.02%
==========================================
Files 35 35
Lines 4415 4428 +13
==========================================
+ Hits 4085 4098 +13
Misses 330 330
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I need to do one last round of manual testing before I merge this. |
I'm going to construct a
allow:
id: root
databases:
fixtures:
allow:
id: root
databases:
fixtures:
tables:
searchable:
allow:
id: root
databases:
fixtures:
queries:
two:
sql: select 1 + 1
allow:
id: root https://gist.github.com/simonw/2d007ebe43de46d44499c77a2a291756 - checkout that Gist to get all four. I manually tested all four scenarios with root and non-root users and confirmed that they worked correctly and padlocks were shown in the right places. |
Refs #1829
check_visibility
method, to cover the newpermissions=
keyword argumentAlso this fix is currently only applied on the table page - needs to be applied on database, row and query pages too.
📚 Documentation preview 📚: https://datasette--1842.org.readthedocs.build/en/1842/