Hi Brick’s team, I wanted to report a bug I encountered while trying to import a remote template in version 2.1.4. When I click import, I run into a class conflict and I’m unable to filter out the specific DWC classes I need to deal with, which is frustrating. In contrast, the older version 2.0.2 allows me to filter and override these conflicts easily. I would appreciate your help in resolving this issue so I can work more efficiently.
The older version was more powerful, but for many if not most users it was confusing & lead to a slower workflow, so we moved to a much simpler accept or reject workflow.
We are still open to re-introducing specific features from the previous class importer if it proves necessary. So just to clarify, is filtering by searching classes the only crucial feature from the previous class importer you need in your workflow, or are there others you rely on regularly?
Hi @charaf , thanks for the info, but that doesn’t address the issue for the current Bricks version… If you notice from the video I linked, the issue is that the classes cannot be filtered, which is a bug that needs to be fixed ASAP for pre 2.2 version, may for 2.1.5. I think it would be great if we don’t have to wait for 2.2 final release to fix this issue.
I think there may be a misunderstanding of my previous reply.
The class filtering functionality you are referring to has been removed altogether since 2.2-rc. The importer was redesigned to be a much simpler accept or reject workflow (see screenshot in my previous reply).
Because of that, creating a patch release for 2.1.x to fix a bug in a feature that is deprecated in the upcoming 2.2 release does not really make sense, especially given that this issue has only been reported once, several months after it was introduced.
So my question was whether providing a search filter in the new 2.2 class importer would be sufficient?
