This repository has been archived by the owner on Jun 1, 2024. It is now read-only.
Releases: ZupIT/beagle-web-react
Releases · ZupIT/beagle-web-react
Release v2.1.0
Todo: release notes should go here
- First Change
- Second Change
Release v2.0.2
Todo: release notes should go here
- First Change
- Second Change
Release v2.0.1
Todo: release notes should go here
- First Change
- Second Change
Release v2.0.0
- All deprecated code has been removed.
- Customizable caching system through the new "ViewClient" service. The ViewClient is built on top of the HttpClient and only serves to retrieve server driven screens, which makes it much easier to implement non-standard behavior for screen requests.
- Navigation context: It is a specialized Context ideal for sending information in a server driven screen stream.
- Updates the Analytics 2:
- It now includes the "rootId" property that reports the id of the first component that appears in the UI tree. This was done as we noticed that some users used this id to identify their screens.
- Since Analytics 1 was deprecated and removed, Analytics 2 now is refered as just Analytics.
- Updates the ScreenComponent:
- The "navigationBar.items[i].action" property has been renamed to "onPress" and now supports multiple actions.
- The "identifier" property has been removed, leaving only "id".
- The "navigationBar.items[i].image" property now accepts Expression, which should be the mobileId of the image.
- Navigation subsystem was refactored to ensure better customization by platforms that use Beagle Web Core (React, Angular and Flutter).
- Loop rendering function has been refactored to ensure interoperability with Beagle Flutter.
- Fixes bug where Text component would not render number 0 or boolean false.
- Fixes bug where Button component did not render non-string text.
- Fixes the "platform" header to send the value expected by the backend: "WEB".
v1.10.2
Patch: fixes the calculation of absolute URL's as first path of a Beagle flow.
Release v1.10.0
Todo: release notes should go here
- First Change
- Second Change
Release v1.9.2
Todo: release notes should go here
- First Change
- Second Change
Release v1.9.1
Todo: release notes should go here
- First Change
- Second Change
Release v1.9.0
Todo: release notes should go here
- First Change
- Second Change
Release v1.7.0
- Fixes problem where the action setContext wouldn’t update a value in the context if the new data type was different than the previous.
- Navigation actions can now recover the context state when navigating back in the history.
- Navigation actions can now further specify aspects of the request to retrieve the view. The new property
httpAdditionalData
lets the backend specify the http method, headers and body of the request. Furthermore, now that the navigation can completely describe a request, the parameternetworkOptions
for creating a Beagle View is no longer required and has been deprecated. - Beagle’s main component,
BeagleRemoteView
, now, besides acceptingroute
as a string (url), also acceptsroute
as an object, which represents a full request, including url, headers, body and method. This also makes the parameternetworkOptions
redundant, so it has been deprecated. CornerRadius
, in the component’s style, now correctly interprets null values.- The component
Text
will now correctly serialize objects and arrays to strings. - Fixes the
z-index
of the componentModal
, which, sometimes, appeared behind other components. - Remote views can now be loaded from endpoints different than the one set in the property
baseUrl
of the configuration. - Fixes problem in the script
beagle init
where the directorysrc
wouldn’t be created if it didn’t previously existed. Also fixed a problem where the script would ask to replace an existing file even if the file didn’t exist.