You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In hindsight, borrowing from HTML's entry list construction and name-value pair conversion for serializing fields in action submission is overkill and introduces artifacts (e.g., newline normalization) that are likely only the result of HTML's historical baggage. I recommend this be simplified so that a Field's value is the thing sent to the server. Since value's type is parameterized, the serialization can be driven by that. For example, when type is date and value is a Date object, serialize to YYYY-MM-DD. When type is file, value should be of type File, or if multiple is set to true, it should be File[].
The text was updated successfully, but these errors were encountered:
… Models (#13)
Remove `SirenClient` class in favor of top-level functions (see below).
Remove support for Node.js.
Add `follow`, `submit`, and `parse` functions.
Add TypeDoc for automated doc generation.
Absorb Siren element classes from `@siren-js/core`.
Simplify default serializer.
Resolves: #11, #12, #17
In hindsight, borrowing from HTML's entry list construction and name-value pair conversion for serializing fields in action submission is overkill and introduces artifacts (e.g., newline normalization) that are likely only the result of HTML's historical baggage. I recommend this be simplified so that a
Field
'svalue
is the thing sent to the server. Sincevalue
's type is parameterized, the serialization can be driven by that. For example, whentype
isdate
andvalue
is aDate
object, serialize toYYYY-MM-DD
. Whentype
isfile
,value
should be of typeFile
, or ifmultiple
is set totrue
, it should beFile[]
.The text was updated successfully, but these errors were encountered: