home / github

Menu
  • GraphQL API

issues_labels

Table actions
  • GraphQL API for issues_labels

65 rows where labels_id = 1913901969

✎ View and edit SQL

This data as json, CSV (advanced)

Link labels_id issues_id
582517965,1913901969 authentication-and-permissions 1913901969 Ability for a canned query to write to the database 582517965
582526961,1913901969 authentication-and-permissions 1913901969 Authentication (and permissions) as a core concept 582526961
628003707,1913901969 authentication-and-permissions 1913901969 Ability to sign in to Datasette as a root account 628003707
628025100,1913901969 authentication-and-permissions 1913901969 Datasette secret mechanism - initially for signed cookies 628025100
628087971,1913901969 authentication-and-permissions 1913901969 Documentation page describing Datasette's authentication system 628087971
628089318,1913901969 authentication-and-permissions 1913901969 "datasette publish" should bake in a random --secret 628089318
628121234,1913901969 authentication-and-permissions 1913901969 /-/permissions debugging tool 628121234
631931408,1913901969 authentication-and-permissions 1913901969 Canned query permissions mechanism 631931408
631932926,1913901969 authentication-and-permissions 1913901969 allow_by_query setting for configuring permissions with a SQL statement 631932926
632753851,1913901969 authentication-and-permissions 1913901969 Release Datasette 0.44 632753851
632918799,1913901969 authentication-and-permissions 1913901969 Permission check for every view in Datasette (plus docs) 632918799
633066114,1913901969 authentication-and-permissions 1913901969 Refactor permission check for canned query 633066114
633578769,1913901969 authentication-and-permissions 1913901969 Support "allow" block on root, databases and tables, not just queries 633578769
634112607,1913901969 authentication-and-permissions 1913901969 Ability to customize what happens when a view permission fails 634112607
634139848,1913901969 authentication-and-permissions 1913901969 Mechanism for specifying allow_sql permission in metadata.json 634139848
634663505,1913901969 authentication-and-permissions 1913901969 Group permission checks by request on /-/permissions debug page 634663505
634844634,1913901969 authentication-and-permissions 1913901969 Drop resource_type from permission_allowed system 634844634
634917088,1913901969 authentication-and-permissions 1913901969 Example permissions plugin 634917088
635108074,1913901969 authentication-and-permissions 1913901969 Example authentication plugin 635108074
635147716,1913901969 authentication-and-permissions 1913901969 Way to enable a default=False permission for anonymous users 635147716
635519358,1913901969 authentication-and-permissions 1913901969 Document the ds_actor signed cookie 635519358
636426530,1913901969 authentication-and-permissions 1913901969 Ability to set ds_actor cookie such that it expires 636426530
636614868,1913901969 authentication-and-permissions 1913901969 It would be more intuitive if "allow": none meant "no-one can do this" 636614868
636722501,1913901969 authentication-and-permissions 1913901969 Having view-table permission but NOT view-database should still grant access to /db/table 636722501
637253789,1913901969 authentication-and-permissions 1913901969 /-/metadata and so on should respect view-instance permission 637253789
637363686,1913901969 authentication-and-permissions 1913901969 Mechanism for skipping CSRF checks on API posts 637363686
637365801,1913901969 authentication-and-permissions 1913901969 actor_matches_allow fails to consider all keys 637365801
641460179,1913901969 authentication-and-permissions 1913901969 Respect default scope["actor"] if one exists 641460179
647095487,1913901969 authentication-and-permissions 1913901969 "datasette -p 0 --root" gives the wrong URL 647095487
647103735,1913901969 authentication-and-permissions 1913901969 "Logged in as: XXX - logout" navigation item 647103735
649329013,1913901969 authentication-and-permissions 1913901969 Only show "log out" button if user is authenticated using a ds_actor cookie 649329013
665400224,1913901969 authentication-and-permissions 1913901969 "allow": true for anyone, "allow": false for nobody 665400224
665403403,1913901969 authentication-and-permissions 1913901969 Allow documentation doesn't explain what happens with multiple allow keys 665403403
665407663,1913901969 authentication-and-permissions 1913901969 Interactive debugging tool for "allow" blocks 665407663
730802994,1913901969 authentication-and-permissions 1913901969 Database download should implement cascading permissions 730802994
732939921,1913901969 authentication-and-permissions 1913901969 Default menu links should check a real permission  732939921
770598024,1913901969 authentication-and-permissions 1913901969 Efficiently calculate list of databases/tables a user can view 770598024
957310278,1913901969 authentication-and-permissions 1913901969 `default_allow_sql` setting (a re-imagining of the old `allow_sql` setting) 957310278
957315684,1913901969 authentication-and-permissions 1913901969 Rename settings to `default_allow_facet` and `default_allow_download` and `default_allow_csv_stream` 957315684
1138008042,1913901969 authentication-and-permissions 1913901969 "permissions" propery in metadata for configuring arbitrary permissions 1138008042
1175690070,1913901969 authentication-and-permissions 1913901969 Reconsider ensure_permissions() logic, can it be less confusing? 1175690070
1175894898,1913901969 authentication-and-permissions 1913901969 Consider simplifying permissions for 1.0 1175894898
1182141761,1913901969 authentication-and-permissions 1913901969 Idea: `datasette.set_actor_cookie(response, actor)` 1182141761
1396948693,1913901969 authentication-and-permissions 1913901969 Table/database that is private due to inherited permissions does not show padlock 1396948693
1397084281,1913901969 authentication-and-permissions 1913901969 If user can see table but NOT database/instance nav links should not display 1397084281
1420090659,1913901969 authentication-and-permissions 1913901969 Private database page should show padlock on every table 1420090659
1421552095,1913901969 authentication-and-permissions 1913901969 Default API token authentication mechanism 1421552095
1423336089,1913901969 authentication-and-permissions 1913901969 `datasette create-token` ability to create tokens with a reduced set of permissions 1423336089
1423336122,1913901969 authentication-and-permissions 1913901969 allow_signed_tokens setting for disabling API signed token mechanism 1423336122
1423347412,1913901969 authentication-and-permissions 1913901969 Prevent API tokens from using /-/create-token to create more tokens 1423347412
1423364990,1913901969 authentication-and-permissions 1913901969 `max_signed_tokens_ttl` setting for a maximum duration on API tokens 1423364990
1423369494,1913901969 authentication-and-permissions 1913901969 datasette create-token CLI command 1423369494
1434094365,1913901969 authentication-and-permissions 1913901969 Tool for simulating permission checks against actors 1434094365
1447465004,1913901969 authentication-and-permissions 1913901969 Ability to create new tokens via the API 1447465004
1485488236,1913901969 authentication-and-permissions 1913901969 "permissions" blocks in metadata.json/yaml 1485488236
1485757511,1913901969 authentication-and-permissions 1913901969 register_permissions(datasette) plugin hook 1485757511
1486011362,1913901969 authentication-and-permissions 1913901969 register_permissions() plugin hook 1486011362
1490576818,1913901969 authentication-and-permissions 1913901969 `/-/permissions` should list available permissions 1490576818
1493306655,1913901969 authentication-and-permissions 1913901969 `view-instance` should not be checked for /-/actor.json 1493306655
1493339206,1913901969 authentication-and-permissions 1913901969 `datasette --get` mechanism for sending tokens 1493339206
1493390939,1913901969 authentication-and-permissions 1913901969 UI to create reduced scope tokens from the `/-/create-token` page 1493390939
1495431932,1913901969 authentication-and-permissions 1913901969 `datasette.create_token(...)` method for creating signed API tokens 1495431932
1495716243,1913901969 authentication-and-permissions 1913901969 Improvements to /-/create-token restrictions interface 1495716243
1497288666,1913901969 authentication-and-permissions 1913901969 Handle abbreviations properly in permission_allowed_actor_restrictions 1497288666
1805076818,1913901969 authentication-and-permissions 1913901969 API tokens with view-table but not view-database/view-instance cannot access the table 1805076818

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [issues_labels] (
   [labels_id] INTEGER REFERENCES [labels]([id]),
   [issues_id] INTEGER REFERENCES [issues]([id]),
   PRIMARY KEY ([issues_id], [labels_id])
);
CREATE INDEX [idx_issues_labels_issues_id]
                ON [issues_labels] ([issues_id]);
CREATE INDEX [idx_issues_labels_labels_id]
                ON [issues_labels] ([labels_id]);
Powered by Datasette · Queries took 10.688ms · About: simonw/datasette-graphql