fix(interaction-output): adjust storing behavior and return type of value method

[JKRhb]

While dealing with the InteractionOutput class, I noticed that a small bug (due to the != null check) was introduced that prevents already parsedValues of type null from being properly returned. This PR solves the issue by replacing the check with !== undefined, so that null values are not being ignored anymore.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (5dc47c4) 77.60% compared to head (fcfe687) 77.61%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1211   +/-   ##
=======================================
  Coverage   77.60%   77.61%           
=======================================
  Files          83       83           
  Lines       17311    17313    +2     
  Branches     1747     1747           
=======================================
+ Hits        13435    13437    +2     
  Misses       3840     3840           
  Partials       36       36           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[JKRhb]

A general related question: Shouldn't the return type of this method rather be Promise<DataSchemaValue> instead of a generic Promise<T>?

[relu91]

A general related question: Shouldn't the return type of this method rather be Promise<DataSchemaValue> instead of a generic Promise<T>?

The correct way should be:

value<T extends DataSchemaValue>(): Promise<T>

This should allow the user to do funny stuff like:

 const b = await output.value<string>() // b inferred to be string without casting

Note: this is something experimental that only works for node-wot users, is not coming from the scripting API

[JKRhb]

Thank you @relu91! I incorporated your feedback in fcfe687 :)

[relu91]

Thanks! Good to go!