-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shall we expose toolkit-specific Ids through ToolkitId methods? #15
Comments
Happy to get this added from my end |
Agreed |
As I stated here, I'm more than happy with this. |
Cool, how would you name the method? |
I think I'd go for |
In Revit_Toolkit we have |
I would not be against duplication - intuitive for all users. |
Sounds like the sensible choice to me too. |
Following the discussion in BHoM/BHoM_Adapter#288, I believe that adding toolkit-specific Query methods returning toolkit-specific Ids would be an easy yet nice UX booster - the currently available generic
AdapterId
method is hard to capture for non-expert users who do not know whatAdapterIdFragmentType
is. Therefore, I think we should add methods likeRobotId
,EtabsId
etc. that would simply callAdapterId
. Looks like we have an initial agreement on that, but just to confirm, what do you think?The text was updated successfully, but these errors were encountered: