missing multiple keyrefs constraints #396

Activity

1. overseers-desk

   assigned

   darakhbharat

   on Oct 26, 2020
2. darakhbharat commented on Oct 26, 2020

   

   darakhbharat

   on Oct 26, 2020

   Contributor

   More actions

   Below are the list of possible elements where "contract" attribute occurs. Now need to update the schema to check if its respective <ts:contract name="" .../> element should occur in XML.

   <ts:ethereum contract="unicon"/>
   <ethereum:call function="redeemed" contract="unicon" as="bool">
   <ethereum:transaction function="setText" contract="PublicResolver" as="bool">
   <ethereum:event type="NameRegistered" contract="ETHRegistrarController" filter="label=${tokenId}" select="name"/>
   
3. overseers-desk

   changed the title [-]missing multiple keyrefs[/-] [+]missing multiple keyrefs constraints[/+] on Oct 27, 2020
4. darakhbharat commented on Oct 31, 2020

   

   darakhbharat

   on Oct 31, 2020

   Contributor

   More actions

   1. contract name keyref is not set up.
      This is completed and tested with changes - darakhbharat@38a09be

   Added ts:contract/@name reference check for above mentioned elements.

   We can directly merge this changes to master as these works on schema 1.0 and are independent of XSD 1.1 validation.