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
We can discuss what is meant here in terms of implementation. The idea is that groups that allow access like boundary_conditions["<name>"] should generate a singular class so that they can be instantiated via the singular name, which is more natural. Note also that the broader name boundary_condition makes senses as the type to use because the zone_type can always be set. Ideally, you want to be able to call set_zone_type() without invalidating the Python object. The other problem is that set_zone_type() is agroupl-level method anyway, so that if you were to call cold_inlet.set_zone_type() you would still have to qualify the call with the name of self.
The text was updated successfully, but these errors were encountered:
Research the possibility of code like this:
We can discuss what is meant here in terms of implementation. The idea is that groups that allow access like
boundary_conditions["<name>"]
should generate a singular class so that they can be instantiated via the singular name, which is more natural. Note also that the broader nameboundary_condition
makes senses as the type to use because thezone_type
can always be set. Ideally, you want to be able to callset_zone_type()
without invalidating the Python object. The other problem is thatset_zone_type()
is agroupl-level method anyway, so that if you were to callcold_inlet.set_zone_type()
you would still have to qualify the call with the name ofself
.The text was updated successfully, but these errors were encountered: