Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Duplicate redux store keys prohibit correct path resolution

Description

ran into an issue in ui-users under settings where the execution similar to:

didn't work for this manifest:

and the path was not resolved correctly.

This is because it looks like redux store contains duplicate keys for active record:

one holds the correct data (ownerId) but the other one is empty.

The feefinestable#folio_users_activeRecord exists because of the dataKey passed in settings:

https://github.com/folio-org/stripes-smart-components/blob/20846e21149a28183d138668755501418e54d5b9/lib/Settings/Settings.js#L43

We are not sure why the other key is also present.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Zak Burke November 22, 2024 at 6:56 PM

, That would help us eliminate redux within stripes-connect, but would allow the stripes-connect API to persist within apps. I don’t see that as a worthwhile gain.

John Coburn November 22, 2024 at 2:48 PM
Edited

As we funnel/centralize dependencies, should we spike to possibly convert stripes-connect to react-query under-the-hood? ( don’t even know if it’s technically possible, hence the spike)

Zak Burke November 12, 2024 at 5:12 PM

This is definitely a bug, but I’m not inclined to fix it. Instead, we recommend that applications refactor away from stripes-connect.

Won't Do

Details

Assignee

Reporter

Labels

Priority

Development Team

Stripes Force

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 11, 2020 at 5:43 PM
Updated December 23, 2024 at 6:05 PM
Resolved December 23, 2024 at 6:05 PM
TestRail: Cases
TestRail: Runs