Skip to content

Conversation

@mhamann-ubl
Copy link
Contributor

@mhamann-ubl mhamann-ubl commented Dec 11, 2025

Purpose

While adding additionalCallNumbers to the inventorys' item history as requested per this user story: https://folio-org.atlassian.net/browse/UIIN-3540 we noticed, that objects are currently being displayed as unordered, unnamed lists. This seems to be deficient as the user has to guess which value belongs to which property.

Approach

We define and pass a customItemFormatter to the AuditLogModal which allows us to display object properties as name-value pairs.

See screenshots.

Refs

https://folio-org.atlassian.net/browse/UIIN-3540

Screenshots

Screenshot from 2025-12-11 15-54-34

@github-actions
Copy link

github-actions bot commented Dec 11, 2025

Jest Unit Test Results

    1 files  ±0    316 suites  ±0   10m 14s ⏱️ +8s
1 389 tests ±0  1 365 ✅  - 5  19 💤 ±0  5 ❌ +5 
1 403 runs  ±0  1 379 ✅  - 5  19 💤 ±0  5 ❌ +5 

For more details on these failures, see this check.

Results for commit 58aadb6. ± Comparison against base commit b863568.

♻️ This comment has been updated with latest results.

elsenhans

This comment was marked as outdated.

@elsenhans elsenhans marked this pull request as draft December 11, 2025 16:15
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
4.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

@elsenhans
Copy link
Contributor

Will be done here:
#2953

@elsenhans elsenhans closed this Dec 18, 2025
@elsenhans elsenhans deleted the UIIN-3540-add-formatting-to-additional-call-numbers branch December 18, 2025 11:27
elsenhans added a commit to folio-org/stripes-components that referenced this pull request Dec 22, 2025
# Description
These changes add the possibility to pass a customItemFormatter to the
AuditLogModal and add to this Formatter the collectionName.

# Why is this change necessary?
While adding additionalCallNumbers to the inventorys item history as
requested per this user story:
https://folio-org.atlassian.net/browse/UIIN-3540 we noticed, that
objects are currently being displayed as unordered, unnamed lists. This
seems to be deficient as the user has to guess which value belongs to
which property.

By adding a custom formatter, we are able to display these objects like
this:

<img width="2978" height="1269" alt="Screenshot from 2025-12-11
15-54-34"
src="https://github.com/user-attachments/assets/8ea804fd-6dcf-4dea-8825-c931c1b9b171"
/>

# Related changes

## Mod-Audit
folio-org/mod-audit#229

## UI-Inventory
folio-org/ui-inventory#2950

---------

Co-authored-by: elsenhans <elsenhans@users.noreply.github.com>
Co-authored-by: elsenhans <48911833+elsenhans@users.noreply.github.com>
github-actions bot pushed a commit to folio-org/stripes-components that referenced this pull request Dec 22, 2025
# Description
These changes add the possibility to pass a customItemFormatter to the
AuditLogModal and add to this Formatter the collectionName.

# Why is this change necessary?
While adding additionalCallNumbers to the inventorys item history as
requested per this user story:
https://folio-org.atlassian.net/browse/UIIN-3540 we noticed, that
objects are currently being displayed as unordered, unnamed lists. This
seems to be deficient as the user has to guess which value belongs to
which property.

By adding a custom formatter, we are able to display these objects like
this:

<img width="2978" height="1269" alt="Screenshot from 2025-12-11
15-54-34"
src="https://github.com/user-attachments/assets/8ea804fd-6dcf-4dea-8825-c931c1b9b171"
/>

# Related changes

## Mod-Audit
folio-org/mod-audit#229

## UI-Inventory
folio-org/ui-inventory#2950

---------

Co-authored-by: elsenhans <elsenhans@users.noreply.github.com>
Co-authored-by: elsenhans <48911833+elsenhans@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants