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
The Env class and the Data trait are vestigial by this point in the Masonry codebase.
There is currently no support for updating widgets when the Env is changed, and I have no intention of adding that support (Xilem seems to be moving in the same direction). This means Env is basically just a way to pass a singleton around in Widget code.
We should remove Env and data, and just hardcode the values that we currently get from Env, with future plans to pass them as arguments or something. Frontend frameworks might still use something Env-like to get style data, but that'll be their responsibility.
The text was updated successfully, but these errors were encountered:
The Env class and the Data trait are vestigial by this point in the Masonry codebase.
There is currently no support for updating widgets when the Env is changed, and I have no intention of adding that support (Xilem seems to be moving in the same direction). This means Env is basically just a way to pass a singleton around in Widget code.
We should remove Env and data, and just hardcode the values that we currently get from Env, with future plans to pass them as arguments or something. Frontend frameworks might still use something Env-like to get style data, but that'll be their responsibility.
The text was updated successfully, but these errors were encountered: