[UXPROD-1991] Stripes: Improve handling of cross-module URL's Created: 12/Aug/19  Updated: 04/Feb/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Khalilah Gambrell Assignee: Khalilah Gambrell
Resolution: Unresolved Votes: 0
Labels: NFR, tech-debt, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-961 Allow Inventory Instances to generate... Closed
Relates
relates to STCOR-410 Implement Cross-module URL registration. Closed
relates to FOLIO-2088 RFC - handling of cross-module URL's Open
relates to STCOR-411 Implement Cross-module-URL requesting Closed
Front End Estimator: John Coburn
Development Team: Stripes Force
PO Rank: 0

 Description   

The Problem: throughout platform-core, ui-modules use links to detail records within other modules, hard-coding urls complete with query parameters. This creates a fragile coupling between modules, as one module can't change its own urls for sake of the other modules using them.
This RFC is to collect and discuss ideas for possible solutions a list thus far (updated as we go):

  • simply document the URLs of a module's workflows.
  • create a mapping in a module's package.json of exposed paths - and allow other ui-modules to ingest this rather than hard-code hrefs.


 Comments   
Comment by John Coburn [ 16/Nov/19 ]

FOLIO-2088 Open Can be implemented in 2 sprints... This would include the stripes-core work to create/expose the API and pick 2 inter-linking modules to integrate the work (ui-check-out and ui-users)

Comment by John Coburn [ 16/Nov/19 ]

I removed the association with the SPIKE to temporarily save form progress. I think a system to handle that would be completely separate from this and would be best to be estimated on its own.

Generated at Fri Feb 09 00:20:12 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.