github atom36942/atom v18.0.0
Atom 18.0.0

latest releases: v18.3.1, v18.3.0, v18.2.0...
one hour ago

Upgrade (projects must change): config_permission_table_write_allowed is replaced by config_permission_table, one permission id per table and action: config_permission_table_write_allowed = ["task"] becomes config_permission_table = {**base_config_permission_table, "task": {"update": 211, "delete": 212}} (from config import config_permission_table as base_config_permission_table), each id labelled in config_column_int_mapping["users"]["permissions"], from 200 and used by no route. Permissions 59 and 60 grant nothing any more: move each user holding them to the new ids (/admin/user-update, permissions), and drop 59 and 60 from every user (they are no longer labelled, so an update that keeps them is refused). /permission/object-delete takes table in the query (?table=task, body {"ids": [...]}). Startup names the old setting.

  • Object permissions per table and action: /permission/object-create, /permission/object-read, /permission/object-read-export (new), /permission/object-update and /permission/object-delete check config_permission_table[table][action] in the middleware: a user may read tickets without deleting them, or edit one table without another. A table or action not in the map is refused. Startup refuses an unknown action, users in the map, an id used twice, used by a route or without a label (docs/auth.md).
  • Root holds every admin and permission flow: at each startup root gets every /admin/* and /permission/* route id with a permission check (86, 61, 62) and every config_permission_table id, Atom's and the project's, exactly that list. A project's other permission routes stay for the users it grants.
  • Tickets: a new Atom table ticket (type Support, Feedback, Bug; status To Do, In Progress, Blocked, Review, Done; title, description, email, reply), created from any page with /my/object-create or, without login, /public/object-create (now rate limited, 10 a minute per caller). The support team works them on the new page /page/ticket (any role, with read 120, update 121, delete 122; light, in the apps' navy look): filters, status and reply, delete, CSV export (docs/crud.md).

Don't miss a new atom release

NewReleases is sending notifications on new releases.