Shore up Users variables support or remove from codebase
Bug #1670860 reported by
Thomas Maddox
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| craton |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Currently we have a partial implementation of variables support for users. It'd be good to finish implementing that, or remove that support entirely. Leaving it partially implemented is prone to weird side effects and bugs.
This came up as a point of concern on https:/
Revision history for this message
| Jim Baker (jimbaker) wrote | #1 |
| Changed in craton: | |
| status: | New → Confirmed |
To post a comment you must log in.
Mixin support should in itself will not cause side effects/bugs, so long as the modeling constraints are maintained. Now that users are only constructed via model code, this is no longer a problem. However, we are missing the ability to use this support.
This functionality was intended to support workflows, so that running a workflow could use some of this user's context. But we are some way from the actual implementation of workflows as a priority.