RFC4912 required a <type> for a named type that defines a type

[overseers-desk]

1. merge this together with RFC4912 required a <type> for a named type that defines a type TokenScript-Examples#93

2. Don't merge this in until both αW can handle the new schema.

[hboon]

@colourful-land should this require a new schema version since 2020/06 has already been shipped?

[overseers-desk]

@colourful-land should this require a new schema version since 2020/06 has already been shipped?

I was hoping to sneak that in since we can't do a new schema version until 2021. The αW can be written to handle both cases (<type> clearly defined or missing out). If you use xpath it should be easy to include the case with <type> or not

[hboon]

@colourful-land should this require a new schema version since 2020/06 has already been shipped?

I was hoping to sneak that in since we can't do a new schema version until 2021. The αW can be written to handle both cases (<type> clearly defined or missing out). If you use xpath it should be easy to include the case with <type> or not

We can do that in an updated app version. But the older versions in the install base will pick up the updated TokenScript files that includes this change like this [1] and break.

[1] https://github.com/AlphaWallet/TokenScript-Examples/pull/93/files

[overseers-desk]

@hboon exactly. How about we make αW android/ios both compatible with both format and wait a few weeks to see how many users upgraded before updating the Repo server?

[hboon]

@colourful-land I don't mind either way. You and @James-Sangalli decide then :)

[overseers-desk]

2\. Don't merge this in until both αW can handle the new schema.

We are getting there. It's been 3 days and the 3.0.5 user base has just surpassed the 3.0.2 user base. I hope by the end of this week we can merge this in already.

[overseers-desk]

Usage of the Android version that didn't support <type> dropped to 15% (iOS should have fallen below this many days ago), so merging this in. I used merge instead of squash because this branch has a fork that is in PR to be merged soon