Microservices have supported a form of dependency injection, but in Beamable 1.10.0, you can use the same dependency injection conventions that the Unity SDK uses. Now, those operations are done in bulk which improves the performance dramatically. Previously, anytime large sections of content were added or removed, the operation would happen serially for each content object. Additionally, large-scale content interactions with the Content Manager are much faster in Beamable 1.10.0. The new process uses a class called ContentDatabase which does a single file scan and caches data until the next domain reload. Now, in Beamable 1.10.0, the FindAssets call has been removed and replaced with a custom solution. Previously, Beamable used an AssetDatabase.FindAssets call during Unity domain reloads to fetch and manage local Beamable Content. Read about the new SDK on the Beamable documentation pages. The new SDK exposes critical user stats like alias and avatar, as well as their credential information. Instead of manually managing TokenResponse structures, you can now use the BeamContext.Accounts. Previously, in order to switch the active Beamable account, the only way was to use the ApplyToken method.
In Beamable 1.10.0, we added a new accounts SDK that is observable, serializable, and collection based.
Here are the highlights from the previous month of releases.
0 kommentar(er)
