Need a new permission, "settings.enabled"
Description
Environment
Potential Workaround
blocks
is blocked by
relates to
Checklist
hideTestRail: Results
Activity
Mike Taylor July 14, 2017 at 1:21 PM
I verified that the new folio/testing-backend VM and the folio-testing website both have this new permission – so that, more generally, stripes-core can now register permissions.
Mike Taylor July 13, 2017 at 4:14 PM
Rush-released v2.2.0 of stripes-connect, needed because the changes to stripes-connect's package.json to support permissionSets caused the version of package2md.js in the most recently released stripes-core to barf on it.
... As Wayne says, CI is source of continuous pain.
Mike Taylor July 13, 2017 at 3:21 PM
Well, then next build of the whole-FOLIO-system VM does indeed include the permission, which is good. But in discussion with Wayne it became apparent that client-side permissions don't get included in the backend VMs that we use for UI development. He's fixing this in FOLIO-717. I'm blocked until that's done and I get a new VM.
Mike Taylor July 13, 2017 at 1:13 PM
Wayne: I have pushed the relevant changes:
stripes-core has the permission in its
package.jsonstripes-demo-platform's
postinstallscript generates a module descriptor for stripes-core.
I think the next build of the folio/testing-backend VM should include the permission.
Mike Taylor July 13, 2017 at 1:08 PM
Moving this to STRPCORE, since that's where the resolution will be.
We need
settings.enabledso we can determine whether to show the "Settings" link, just we consultmodule.XXX.enabledto determine whether to show the XXX application. This needs to be a permission – not some other kind of configuration – so it can be included in higher-level permissions such as "Settings (Items): Can create, edit and remove loan types" ().