Closed cboulay closed 10 months ago
Is there a way for a child of ez.Settings to not be allowed to have a field named .settings?
I believe the settings metaclass can check for the existence of a field called settings. That's a warning at most though; I'll accept this for now, but let's make note of delivering a warning in the future.
Settings are typically passed to a Unit upon instantiation as follows (e.g.)
With this change, we can alternatively pass the settings parameters directly to the Unit (without the __Settings class) and they will be used to initialize the settings. i.e.,
It's just a little quality-of-life improvement that makes the entry-point scripts cleaner.
Fixes #71