Tag unstagewrite bugfix

[jhenson29]

changed unstageWriteRequest to set tag.controllerValue to tag.value instead of the other way around.

Description, Motivation, and Context

tag.value returns to previous value after a plc write because it is set to tag.controllerValue in unstageWriteRequest, but tag.controllerValue had never been updated.

How Has This Been Tested?

Tested writing tag to plc.

Screenshots (if appropriate):

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests passed.
• [ ] This is a work in progress, and I want some feedback (If yes, please mark it in the title -> e.g. [WIP] Some awesome PR title)

Related Issue

36

[coveralls]

Pull Request Test Coverage Report for Build 112

• 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 50.982%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/tag/index.js	0	1	0.0%
<!--	Total:	0	1	0.0%	-->

Totals
Change from base Build 110:	0.0%
Covered Lines:	472
Relevant Lines:	883

---

💛 - Coveralls

[cmseaton42]

You are correct on this I think

The only use of the unstageWriteRequest method is to move the value from tag.vlaue to tag.controllervalue once a write has been successful. This way the controllervalue is always up to date with what is in the PLC