[FOLIO-3739] provide ky as a direct-dep in platforms Created: 16/Mar/23 Updated: 22/Mar/23 Resolved: 22/Mar/23 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Zak Burke | Assignee: | Zak Burke |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | stripes-force 161 | ||||||||||||
| Story Points: | 1 | ||||||||||||
| Development Team: | Stripes Force | ||||||||||||
| Release: | Poppy (R2 2023) | ||||||||||||
| RCA Group: | TBD | ||||||||||||
| Description |
|
Summary: ky should be provided as a direct-dependency so other modules can refer to it as a peer. Details: A ky object is provided by @folio/stripes/core::useOkapiKy(), a publicly exported hook. This means other modules will receive the ky object instantiated by stripes-core. In order for both modules to have an understanding of what that object is, they need to share a common definition of it, i.e. they both need to point to that definition as a peer. |
| Comments |
| Comment by Zak Burke [ 22/Mar/23 ] |
|
Discussion at #stripes-architecture concluded, “No, ky should not be a peer. The ‘type’ returned by hooks like useOkapiKy is something like ‘a stripes-wrapped ky object’ rather than ‘a bare ky object’ even if at present that wrapper is very very thin.” |