-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add Query methods for Link Names, Read-only Parameters and spatial elements' bound conditions #1220
Add Query methods for Link Names, Read-only Parameters and spatial elements' bound conditions #1220
Conversation
@BHoMBot check required |
@vietle-bh to confirm, the following checks are now queued:
There are 17 requests in the queue ahead of you. |
@BHoMBot check required |
@vietle-bh to confirm, the following checks are now queued:
There are 21 requests in the queue ahead of you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few points about the PR itself:
- the title is misleading (you are not migrating methods, but adding a property, enum, methods etc.)
- missing labels
- the PR is currently not testable:
- what should I do with the sample Autodesk model? how does it correspond to the 4 bound conditions that we have? I am happy not to get the answers to these questions if agree that this PR will be followed by another PR that will make
RoomFromRevit
andSpaceFromRevit
leverage the concept that you are introducing - would be good to see a simple script (even working on the sample Revit model) that verifies the correct behaviour of
RevitParameter.IsReadOnly
- what should I do with the sample Autodesk model? how does it correspond to the 4 bound conditions that we have? I am happy not to get the answers to these questions if agree that this PR will be followed by another PR that will make
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor things, but we are getting there 👍
@BHoMBot check required |
@vietle-bh to confirm, the following actions are now queued:
There are 344 requests in the queue ahead of you. |
Sorry @FraserGreenroyd , the post-build event check under |
@BHoMBot check project-compliance |
@vietle-bh to confirm, the following actions are now queued:
There are 9 requests in the queue ahead of you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am happy with the code, but could you please make the PR title a bit more informative? Along the lines: Link name and spatial bound queries added along with Parameter.IsReadOnly property
Btw I agree with @vietle-bh regarding the failing project compliance check: it looks like an error on the bot side @FraserGreenroyd? |
Thanks. I have changed the PR name now. |
Thanks @pawelbaran . FYI, I also currently have this same bug(?) on 3 other PRs here, here and here. |
@BHoMBot check versioning |
@vietle-bh to confirm, the following actions are now queued:
|
@pawelbaran to confirm, the following actions are now queued:
There are 11 requests in the queue ahead of you. |
@BHoMBot check installer |
@vietle-bh to confirm, the following actions are now queued:
There are 9 requests in the queue ahead of you. |
@BHoMBot check project-compliance |
@vietle-bh to confirm, the following actions are now queued:
|
@BHoMBot check installer |
@pawelbaran to confirm, the following actions are now queued:
There are 3 requests in the queue ahead of you. |
@BHoMBot check ready-to-merge |
@pawelbaran to confirm, the following actions are now queued:
There are 7 requests in the queue ahead of you. |
Issues addressed by this PR
Closes #1219
IsReadOnly
property toRevitParameter
Test files
Please use the sample model "rac_basic_sample_project" that comes with Revit, or any model that contains rooms.
Changelog
IsReadOnly
property toRevitParameter