[FOLIO-1769] When should a UI module state dependency on an interface? Created: 01/Feb/19 Updated: 25/Jan/23 Resolved: 25/Jan/23 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Marc Johnson | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | potential-decision | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
When a UI module starts to endpoints provided as part of an interface, when should the module start declaring a dependency upon the interface? Options (Please edit to add further options if I have missed any) Should this:
|
| Comments |
| Comment by Marc Johnson [ 01/Feb/19 ] |
|
Julian Ladisch Kostyantyn Khodarev Oleksii Maksymov Please amend this if the description does not fit the situation we have been discussing. Jakub Skoczen Adam Dickmeiss I've marked this as for the core platform team, as I believe this team owns policies like this. Please feel free to reassign / un-assign as you see fit. |