Releases: siren-js/client
Releases · siren-js/client
v0.9.0
Added
- Support for element traversal via the Visitor pattern (#14)
DefaultSirenElementVisitorfor visitors that don't need to visit every type of elementLinkFinderfor searching an entity's linksActionFillerfor populating an action's fieldsCompositeVisitorfor composing multiple visitors
- Support for crawling an API via
crawl(#15) - Support for validating fields on action submission (#16)
- Default JSON serializer (#27)
- Advanced
submitusage examples in the JSDocs - Default serializer is available for extension (see
submitdocs)
Changed
- Links to source in the docs are no longer generated
v0.8.2
v0.8.1
v0.8.0
Added
resolvefunction for resolving aSubEntity- Development section in the README
Changed
- Project is now built with Node 18
Removed
- Contribution guidelines and code of conduct, which now live here
v0.7.0
NOTE: This release includes breaking changes from v0.6.0.
Added
- Support for relative URLs (#21)
Changed
- For supporting relative URLs (#21),
follow'sRequestInitparameter is now nested in an options object Serialization'scontentTypeis now optional- The default serializer no longer requires
checkboxfields to use thecheckedextension (#22)
Fixed
- Submitting a
multipart/form-dataaction now includes theboundaryparameter (#23)
v0.6.2
v0.6.1
v0.6.0
NOTE: This release includes breaking change from v0.5.0.
Removed
SirenClienthas been removed in favor of top-level functions (see below)- Support for Node.js has been removed (for now), primarily for serialization simplification (#17). Including polyfills for
FileandFormDatamay resolve this.
Added
Changed
v0.5.0
v0.4.0
Added
- Support for custom serializers
- Default serializer for
text/plainactions
Changed
- Upgraded
@siren-js/coreto v0.3.2 - Aligned newline normalization with HTML's algorithm for
converting an entry list to a list of name-value pairs, which
normalizes newlines in fields'names and values during action submission.