User Details
- User Since
- Jan 5 2021, 4:31 PM (77 w, 3 d)
- Availability
- Available
- LDAP User
- Cory Massaro
- MediaWiki User
- CMassaro (WMF) [ Global Accounts ]
Today
Yesterday
Fri, Jun 24
Wed, Jun 22
Deprecate function-schemata/utils.js:convertZListToArray method (or modify it to convert these lists to benjamin arrays instead
Fri, Jun 17
Tue, Jun 14
Mon, Jun 13
Tue, Jun 7
Mon, Jun 6
Fri, Jun 3
This is also causing a warning to surface from convertZListToArray; this is because we create a schema for typed lists whose types we don't resolve.
Thu, Jun 2
May 31 2022
May 26 2022
SO. This is happening because we're reading data definitions from function-schemata (where the files have all been Benjamin-ized). This only matters in the case of Z13, which we probably shouldn't be using anyway. Replacing the reference to Z13 in the test with a literal empty list should fix it.
May 24 2022
May 23 2022
May 19 2022
May 17 2022
May 6 2022
I'm not convinced we should do this but happy to discuss.
May 5 2022
May 4 2022
May 3 2022
May 2 2022
Apr 29 2022
Apr 28 2022
This is no longer valid since the reference functions have been deleted.
Apr 26 2022
Apr 25 2022
In the interests of backwards-compatibility, I request that we add a Boolean parameter aboutTheBenjamins=false (or something); otherwise, we'll end up making breaking changes in the consuming repositories.
In the interests of backwards-compatibility, I request that we add a Boolean parameter aboutTheBenjamins=false (or something); otherwise, we'll end up making breaking changes in the consuming repositories.
Apr 21 2022
Apr 19 2022
Apr 18 2022
Apr 15 2022
Apr 13 2022
For what it's worth, Python doesn't even do this. I can happily define a function
We can now close this.
Apr 12 2022
Apr 11 2022
This was fixed when we fixed this task. I have added your exact ZObjects (ZIDs changed for anonymity) as a test in the orchestrator.
Apr 8 2022
Apr 7 2022
Apr 6 2022
Hmm, maybe it's not totally correct. The return value looks like this:
Yes, that is exactly the problem. I think Geno's recent patch will have fixed this. In the meantime, I have added this as a test to the orchestrator (with the explicit string form, i.e. Z3K2: { Z1K1: 'Z6', Z6K1: 'K1' }), which gets the correct result (a Z4).
Apr 5 2022
Apr 4 2022
Mar 29 2022
Mar 23 2022
Can we move this to phase Theta?