Post #1795138
2026-04-27 12:08 UTC
@muep It was done that way to maintain backward compatibility with earlier versions of Ring. Form parameters are a difficult compromise because while parameter names are not required to be unique, in practice it's quite rare to use duplicate names, as its usually better to use explicit IDs than rely on implicit ordering for identification.
Replies (1)
-
@muep@mastodontti.fi 2026-04-27 12:15
@weavejester thanks for the background. It sure did look like changing it would break API consumers that expect the current behavior. For my use case, I tried to work around this by adding an extra middleware that wraps the singleton items into vectors, to be easier able to describe the expected schema in the endpoint metadata, and to avoid having to make the endpoints check for it. Didn't get it super right, though.