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
This is for down the line, but to me it seems to make more sense to have one parent class: E.G: AureusLabel, AureusButton, AureusView, AureusCard, etc and have the children inherit from there.
Each one is currently a custom Stateless Widget, and I think as we scale it might be better for everyone to build these parent classes and to standardize all of that code like we do with the BaseBackingDecoration class that covers implementation, and use the subclasses to handle the actual details of it.
Another for the roadmap :-)
The text was updated successfully, but these errors were encountered:
This is for down the line, but to me it seems to make more sense to have one parent class: E.G: AureusLabel, AureusButton, AureusView, AureusCard, etc and have the children inherit from there.
Each one is currently a custom Stateless Widget, and I think as we scale it might be better for everyone to build these parent classes and to standardize all of that code like we do with the BaseBackingDecoration class that covers implementation, and use the subclasses to handle the actual details of it.
Another for the roadmap :-)
The text was updated successfully, but these errors were encountered: