Skip to content

put format in an array to match what front end expects#468

Merged
charmingduchess merged 1 commit intomainfrom
SCC-4563/add-format-filter
Mar 17, 2025
Merged

put format in an array to match what front end expects#468
charmingduchess merged 1 commit intomainfrom
SCC-4563/add-format-filter

Conversation

@charmingduchess
Copy link
Contributor

@charmingduchess charmingduchess commented Mar 13, 2025

The front end is expecting format to be an object in an array. I assume we would like to continue that data structure? I personally feel that it is unnecessary but I do not feel strongly about it either way.

@charmingduchess charmingduchess requested a review from nonword March 13, 2025 20:45
Copy link
Member

@nonword nonword left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We historically cast all data as arrays, even non-repeating values, just to remove uncertainty on the front-end. More recently, this rule has fallen off as we have some properties that are singular. If it's easier to cast it as an array here from the backend, then this is fine; If easier to update the front-end, that's also fine.

@charmingduchess charmingduchess merged commit edd9d2d into main Mar 17, 2025
4 checks passed
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.

2 participants