🐛 Bug fixes

• 7d809e1 fix issue #1071 related to monitored item not respecting accessRestriction
• d547293 improve UAVariable/UAAnalogDataItem write OutOfBound value #1119
• d547293 fix UAVariable setter(value) so that returned StatusCode is applied to the dataValue.statusCode #119
• 17f5518 fix constructBrowsePathFromQualifiedName #1201

🚀 enhancement

• 1b97628 add ability to overide default transport timeout when creating client #1002

📖 documentation and example

• a2ac9ec add example to illustrate answer in #1120
• 643b51e add example to illustrate #1222
• 3b30c7c doc: add example for nodeset_filename option

🪳 minor adjustment & refactoing

• 5686a2c relax event loop in test
• 2a26a65 adjust interactive client
• b0dbc62 refactor: clean up nodeset definition/generation code further
• a8ed0cc refactor: clean up nodeset definition/generation code
• ab9ed0e refactor: rename to correct spelling correponding -> corresponding

👬🏽 contributors

• @AndreasHeine, @maximivanov and @jacobq

improve UAVariable/UAAnalogDataItem write OutOfBound value ( #1119)

• add an optional acceptValueOutOfRange flag to addAnalogItem.
  The acceptValueOutOfRange property indicates whether the write operation will accept or reject
  value which is out of range of the instrumentRange.

• if true: during am writeOperation by a client if the dataValue that is outside of the
  instrumentRange. it will be recorded database and the statusCode will be set to BadOutOfRange, and
  the write operation will return Good. The value will be ecorded in the history database if the variable supports historizing.

• if false: during a writeOperation by a client, if the dataValue that is outside of the
  instrumentRangeit will be denied and the write operation will return BadOutOfRange.