The ideal way to test it, in my humble opinion, is to use this package in Jarbas. The roadmap would look like this:
[x] Get Jarbas running inside this package's Poerty virtualenv so we can import from this package
[x] Delete jarbas/public_admin directory
[x] Create an insance of public_admin.PublicAdminSite in jarbas/dashboard/admin.py (public_apps would be ("chamber_of_deputies",) and public_models would be ("reimbursement",)
[x] Check whether or not this breaks Jarbas Dashboard on the browser
[x] Check whther no-read-only endpoitns are still non-existent
The ideal way to test it, in my humble opinion, is to use this package in Jarbas. The roadmap would look like this:
jarbas/public_admin
directorypublic_admin.PublicAdminSite
injarbas/dashboard/admin.py
(public_apps
would be("chamber_of_deputies",)
andpublic_models
would be("reimbursement",)