12:04:33 RRSAgent has joined #wot-script 12:04:33 logging to https://www.w3.org/2021/03/01-wot-script-irc 12:06:31 cris has joined #wot-script 12:08:29 scribe: zkis 12:08:40 scribenick: cris 12:09:03 Meeting: WoT Scripting 12:09:07 topic: previous minutes 12:09:15 -> see https://www.w3.org/2021/02/22-wot-script-minutes.html 12:09:24 present+ Kaz_Ashimura, Daniel_Peintner, Cristiano_Aguzzi, Zoltan_Kis 12:09:43 present+ Tomoaki_Mizushima 12:09:52 dp: we looked at the f2f wiki, we have to improve it. Maybe discuss again the time frame 12:10:14 ... we merged the a pr from Cris even if it could be improved with more examples 12:10:42 ... then we reviewed issue 302. We decided to not update WebIDL but only TS. 12:11:28 zoltan: btw InteractionInput is any so that's why WebIDL update is unnecessary. 12:11:45 dp: yeah but I prefer to have WebIDL and TS aligned. 12:12:07 ... then we reviewed 293 issue. We have two open PR to solve the issue. We'll discuss later. 12:12:14 ... minutes ok? 12:12:20 zoltan: yes 12:12:36 dp: ok minutes approved. 12:12:41 topic: Quick updates 12:13:47 Mizushima has joined #wot-script 12:14:18 -> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_March_2021#Scripting_.281h.29 12:14:24 dp: about F2F. I modified the topics on the link above 12:14:53 ... the group should provide feedback on that points. 12:15:38 ... then there's the rename to master branch to main. Other groups are converging. Not big issues just some warnings when doing the update. 12:15:55 ... anyhow let's postpone it 12:15:59 topic: PRs 12:16:22 ... Factor out maplike interfaces property reads and writes - https://github.com/w3c/wot-scripting-api/pull/305 12:17:16 dp: Zoltan changed PropertyMap to a maplike object. 12:17:20 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#1_March_2021 12:17:41 zoltan: it has utility methods like forEach 12:17:48 s/281h.29/281h.29 F2F wiki/ 12:17:59 dp: it's fine by me. 12:18:05 ... cristiano also approved it 12:18:10 s/-> see/-> / 12:18:18 s/minutes.html/minutes.html Feb-22/ 12:18:29 +1 12:18:48 s/... Factor/dp: Factor/ 12:18:53 rrsagent, make log public 12:18:58 rrsagent, draft minutes 12:18:58 I have made the request to generate https://www.w3.org/2021/03/01-wot-script-minutes.html kaz 12:19:08 dp: next pr: 12:19:41 -> Introduce PropertyReadMap and PropertyWriteMap in TS - https://github.com/w3c/wot-scripting-api/pull/308 12:19:52 Chair: Daniel 12:20:11 ... is the counterpart of the previous PR, but only for TS 12:20:37 i/Factor out/scribnick: dape/ 12:20:51 dp: it's ok but there are some code style issues. 12:20:51 i/Zoltan changed Pro/scribenick: cris/ 12:20:54 rrsagent, draft minutes 12:20:54 I have made the request to generate https://www.w3.org/2021/03/01-wot-script-minutes.html kaz 12:21:15 cris: I'll fix the issues after the call. 12:21:18 s/scribnick/scribenick/ 12:21:19 rrsagent, draft minutes 12:21:19 I have made the request to generate https://www.w3.org/2021/03/01-wot-script-minutes.html kaz 12:22:06 dp: so let's merge after the call 12:22:09 s/Introduce PropertyReadMap and PropertyWriteMap in TS -// 12:22:16 ... any objections? 12:22:19 s/308/308 PR 308 - Introduce PropertyReadMap and PropertyWriteMap in TS/ 12:22:34 ... ok then I'll also publish and increase the version number 12:22:40 TOPIC: fix 302 - https://github.com/w3c/wot-scripting-api/pull/307 12:23:27 dp: it's about the return type of ActionHandler and invokeAction 12:23:38 s/topic: PRs/topic: PR 305 - Factor out maplike interfaces property reads and writes/ 12:23:40 ... it propose to use undefine. 12:24:59 rrsagent, draft minutes 12:24:59 I have made the request to generate https://www.w3.org/2021/03/01-wot-script-minutes.html kaz 12:25:41 i/PR 308 -/topic: PR 308 - Introduce PropertyReadMap and PropertyWriteMap in TS/ 12:25:51 rrsagent, draft minutes 12:25:51 I have made the request to generate https://www.w3.org/2021/03/01-wot-script-minutes.html kaz 12:26:15 zoltan: are you sure that in TS needs to declare that something can be also undefined? 12:26:19 dp: not sure 12:26:53 cris: I remember some errors in other expirements that I did. I'll have to check. 12:27:13 zoltan: ts is more strict 12:28:21 https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABFApgZygCgJQC4DyARgFYrSIDeAsAFCL2IBOKUIjS4AJisDGCpwDctAL5A 12:29:51 cris: it seems from the link above that you should declare it as undefined or object 12:30:08 dp: so we don't go out of sync? 12:30:20 zoltan: no, as long as the algorithm is clear. 12:30:56 dp: so do we agree to merge? 12:31:03 zoltan: ok 12:31:44 dp: merged 12:32:23 topic: issues 12:32:36 dp: let's start with 306 12:32:37 .. Feedback about InteractionOuput, https://github.com/w3c/wot-scripting-api/issues/306 12:33:04 ... it was originally started by sebastian. 12:33:29 ... we were discussing about having the new api or old apis in this plugfest 12:33:43 ... he wondered how the new api will look like 12:34:23 ... he was not sure that the new api is intuitive 12:34:37 s/topic: issues/topic: Issue 306 12:35:05 ... to summurize, the old api for the simple case was good, but new api can cover more usecases 12:35:41 i|issues/306|issues/306 - Feedback about InteractionOuput| 12:35:45 rrsagent, draft minutes 12:35:45 I have made the request to generate https://www.w3.org/2021/03/01-wot-script-minutes.html kaz 12:36:22 zoltan: the code in the issue it is not really correct. It assumes that you know that a property will return a json value 12:36:47 .... for a complete picture you should add every other bit of code for error handling 12:37:28 ... because the example hides other details 12:37:44 dp: that's true even with the new api 12:37:50 zoltan: true 12:38:24 ... btw in the new api you know immediately where you're failing. 12:39:17 zoltan: there are a couple of option on the issue body 12:39:40 ... thenable it seems the more promising 12:40:04 ... but it might not super uderstood 12:40:15 ... and the only benifit is to remove one await. 12:42:37 cris: thenable are fine, but not sure too if it is really worth 12:43:13 ... value as function as also benefits from TS world. You can define type guards 12:43:50 dp: I think this is a precious feedback from developers, we should pay attention to it. 12:45:10 zoltan: stream can handle all usecases 12:45:26 ... we can look at some examples 12:45:57 dp: currently the runtime decide to provide a stream or a value 12:46:07 zoltan: no it's the application to decide 12:47:11 cris: true 12:48:03 zoltan: if dataUsed is true the application should not use stream interface 12:51:38 dp: if you call value arrayBuffer will fail, should we improve it 12:51:51 cris: yes it might be worth doing it. 12:52:16 zoltan: we don't really have an use case for this 12:52:42 ... it is up to us anyway 12:53:03 dp: it blows up the memory true 12:53:13 zoltan: if it is confusing we could remove it 12:53:42 ... it is equivalent to a readable stream 12:54:09 ... you are rising an other usecase: buffer is similar to value. 12:55:28 dp: I think to have the benifit to having arraybuffer or Readable stream 12:56:05 ... do we know any devices that does not have Readable Stream? 12:56:16 zoltan: zephir os is an example 12:58:13 dp: the consensus seems to be that the current API is in a good shape. 12:59:42 cris: I am good to close it 12:59:50 dp: closed 12:59:53 dp: time is up 13:00:27 [adjourned] 13:00:34 rrsagent, draft minutes 13:00:34 I have made the request to generate https://www.w3.org/2021/03/01-wot-script-minutes.html kaz 14:35:36 Zakim has left #wot-script