Skip to content
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

RevitTypeFragment introduced and BHoM converts fixed to pass the type information to the output object #1174

Merged
merged 12 commits into from
Mar 1, 2022

Conversation

pawelbaran
Copy link
Member

@pawelbaran pawelbaran commented Feb 14, 2022

Issues addressed by this PR

Covers large portion of #1169

Test files

PR-specific test file on SharePoint.
Builders work openings can be tested using this script
BEnv openings can be test using PullBEnvModel from this folder

Changelog

  • RevitTypeFragment introduced
  • BHoM converts fixed to pass the type information to the output object.

Additional comments

Added @enarhi for reference - might be a good inspiration for fixing Facade converts.

Updates to output object:

  • BH.oM.Architecture.BuildersWork.Opening - RevitTypeFragment is added along with Profile, which is not necessarily related to the element type (it is based on parameter values of the element itself)
    • BH.oM.Architecture.Elements.Room - RevitTypeFragment added because the object does not have a defining property
    • BH.oM.Environment.Elements.Opening - fixed to pass the parameters to OpeningConstruction
    • BH.oM.Environment.Elements.Space - RevitTypeFragment added because the object does not have a defining property
    • BH.oM.MEP.System.CableTray - RevitTypeFragment is added along with SectionProperty, which is not related to the element type (it is based on parameter values of the element itself)
    • BH.oM.MEP.System.Duct - RevitTypeFragment is added along with SectionProperty, which is not related to the element type (it is based on parameter values of the element itself)
    • BH.oM.MEP.System.Fittings.Fitting - RevitTypeFragment added because the object does not have a defining property
    • BH.oM.MEP.System.Pipe - RevitTypeFragment is added along with SectionProperty, which is not related to the element type (it is based on parameter values of the element itself)
    • BH.oM.MEP.System.Wire - RevitTypeFragment added because the object does not have a defining property
    • BH.oM.Physical.Elements.Door - convert fixed to create an empty Construction that represents the element type (and contains its parameters)
    • BH.oM.Physical.Elements.Window - convert fixed to create an empty Construction that represents the element type (and contains its parameters)

@pawelbaran pawelbaran added type:bug Error or unexpected behaviour type:feature New capability or enhancement labels Feb 14, 2022
@pawelbaran pawelbaran self-assigned this Feb 14, 2022
@pawelbaran
Copy link
Member Author

@BHoMBot check compliance
@BHoMBot check null-handling

@bhombot-ci
Copy link

bhombot-ci bot commented Feb 14, 2022

@pawelbaran to confirm, the following checks are now queued:

  • code-compliance
  • documentation-compliance
  • project-compliance
  • branch-compliance
  • dataset-compliance
  • copyright-compliance
  • null-handling

@pawelbaran
Copy link
Member Author

@BHoMBot check required

@bhombot-ci
Copy link

bhombot-ci bot commented Feb 14, 2022

@pawelbaran to confirm, the following checks are now queued:

  • code-compliance
  • documentation-compliance
  • project-compliance
  • core
  • null-handling
  • serialisation
  • versioning
  • installer

@pawelbaran
Copy link
Member Author

@BHoMBot check installer

@bhombot-ci
Copy link

bhombot-ci bot commented Feb 15, 2022

@pawelbaran to confirm, the following checks are now queued:

  • installer

@bhombot-ci
Copy link

bhombot-ci bot commented Feb 15, 2022

The check installer has already been run previously and recorded as a successful check. This check has not been run again at this time.

@FraserGreenroyd
Copy link
Contributor

@BHoMBot this is a DevOps instruction. Force check: installer

@pawelbaran
Copy link
Member Author

@BHoMBot check installer

1 similar comment
@pawelbaran
Copy link
Member Author

@BHoMBot check installer

@pawelbaran
Copy link
Member Author

@BHoMBot you there

@bhombot-ci
Copy link

bhombot-ci bot commented Feb 15, 2022

@pawelbaran sorry, I didn't understand.
Was that comment an instruction for me? If so, could you state again what check you would like me to do?
For a list of available instructions, please see this wiki page.

@pawelbaran
Copy link
Member Author

@BHoMBot check installer

@bhombot-ci
Copy link

bhombot-ci bot commented Feb 15, 2022

@pawelbaran to confirm, the following checks are now queued:

  • installer

Copy link
Contributor

@michal-pekacki michal-pekacki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@pawelbaran
Copy link
Member Author

@BHoMBot check copyright-compliance
@BHoMBot check dataset-compliance
@BHoMBot check ready-to-merge

@bhombot-ci
Copy link

bhombot-ci bot commented Mar 1, 2022

@pawelbaran to confirm, the following checks are now queued:

  • copyright-compliance
  • dataset-compliance
  • ready-to-merge

@pawelbaran pawelbaran merged commit 1cf6a24 into main Mar 1, 2022
@pawelbaran pawelbaran deleted the Revit_Toolkit-#1169-RevitTypeHandling branch March 1, 2022 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Error or unexpected behaviour type:feature New capability or enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants