Skip to content

Fix #4084 - Maintain backward compatibility in SubSurface::setShadingControl including with C++ interfaces - #4086

Merged
kbenne merged 2 commits into
developfrom
4084_ShadingControl
Sep 21, 2020
Merged

Fix #4084 - Maintain backward compatibility in SubSurface::setShadingControl including with C++ interfaces#4086
kbenne merged 2 commits into
developfrom
4084_ShadingControl

Conversation

@jmarrec

@jmarrec jmarrec commented Sep 21, 2020

Copy link
Copy Markdown
Collaborator

Pull request overview

In #4066, I made a change in ff629b3 that affects the OS App in particular, see the const that's gone:

-   bool setShadingControl(const ShadingControl& shadingControl);
+  OS_DEPRECATED bool setShadingControl(ShadingControl& shadingControl);

This PR restores it to:

 OS_DEPRECATED bool setShadingControl(const ShadingControl& shadingControl)

and does a const_cast instead.

Pull Request Author

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

  • Model API Changes / Additions
  • Any new or modified fields have been implemented in the EnergyPlus ForwardTranslator (and ReverseTranslator as appropriate)
  • Model API methods are tested (in src/model/test)
  • EnergyPlus ForwardTranslator Tests (in src/energyplus/Test)
  • If a new object or method, added a test in NREL/OpenStudio-resources: Add Link
  • If needed, added VersionTranslation rules for the objects (src/osversion/VersionTranslator.cpp)
  • Checked behavior in OpenStudioApplication, adjusted policies as needed (src/openstudio_lib/library/OpenStudioPolicy.xml)
  • Verified that C# bindings built fine on Windows, partial classes used as needed, etc.
  • All new and existing tests passes
  • If methods have been deprecated, update rest of code to use the new methods

Labels:

  • If change to an IDD file, add the label IDDChange
  • If breaking existing API, add the label APIChange
  • If deemed ready, add label Pull Request - Ready for CI so that CI builds your PR

Review Checklist

This will not be exhaustively relevant to every PR.

  • Perform a Code Review on GitHub
  • Code Style, strip trailing whitespace, etc.
  • All related changes have been implemented: model changes, model tests, FT changes, FT tests, VersionTranslation, OS App
  • Labeling is ok
  • If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
  • If feature, test running new feature, try creative ways to break it
  • CI status: all green or justified

@jmarrec jmarrec added component - Model Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge. labels Sep 21, 2020
@jmarrec jmarrec self-assigned this Sep 21, 2020
@jmarrec

jmarrec commented Sep 21, 2020

Copy link
Copy Markdown
Collaborator Author

locally builds just fine and all tests are clear.

@ci-commercialbuildings

ci-commercialbuildings commented Sep 21, 2020

Copy link
Copy Markdown
Contributor

@kbenne
kbenne merged commit 7e9cd9e into develop Sep 21, 2020
@kbenne
kbenne deleted the 4084_ShadingControl branch September 21, 2020 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component - Model Pull Request - Ready for CI This pull request if finalized and is ready for continuous integration verification prior to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ShadingControl API breakage

3 participants