Skip to content

Update/Create internal Guidelines for developpers #5501

@jmarrec

Description

@jmarrec

Enhancement Request

@joseph-robertson and I have been discussing this periodically, and at some point we ought to do something.

This is going to be a running list of things we should clarify. It would benefit anyone getting onboarded, but it would probably benefit seasoned developers too (I personally don't wrap objects often enough nowadays to remember 100% how to proceed with the clone/remove/children right away, I have to think)

Detailed Description

  • Choice dependent fields
    • Eg Field A is a choice field, Field B is only used if Field A = "Value1" and Field B is only used Field A = "Value2"
    • Should the setFieldA(std::string choice) clear the unused field?
    • If not, should you only translate choice-dependent fields to the IDF?
  • Clarify how you should pick whether something is a ModelObjhect, PArentObject, ResourceObject, HVACComponent

Possible Implementation

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions