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
As mentioned in latest coordination meeting we've noted that the brick:Collections is a subclass of the rec:Collection
Wonder if the brick:Collection is really needed as removing it (deprecating it) would lead to a straighter class hierarchy!?
If it's due to some relationships or properties not present on the rec:Collection we'd be happy to try to solve by upgrading the rec:Collection accordingly
Best Peter
The text was updated successfully, but these errors were encountered:
Hi @PeteHart . We discussed this a little today and I think removing the Brick Collection would be a good idea. I'm in agreement with your comment in #672 , and using includes for Systems would feel more consistent. This is definitely a Brick 1.5 change, but we can make it available sooner through a Brick 1.5 pre-builds (available on #658)
@gtfierro
As mentioned in latest coordination meeting we've noted that the brick:Collections is a subclass of the rec:Collection
Wonder if the brick:Collection is really needed as removing it (deprecating it) would lead to a straighter class hierarchy!?
If it's due to some relationships or properties not present on the rec:Collection we'd be happy to try to solve by upgrading the rec:Collection accordingly
Best Peter
The text was updated successfully, but these errors were encountered: