Project

General

Profile

« Previous | Next » 

Revision 92a4d31c

Added by koszko over 1 year ago

make "uuid" an optional property

View differences:

index.json
78 78 

  		




  79
  79
  
    
	    // "long_name" should be used to specify a user-friendly alternative


  		




  80
  80
  
    
	    // to an identifier. It should generally not collide with a long


  		




  81
  
  
    
	    // name of some resource with a different uuid and also shouldn't


  		




  
  81
  
    
	    // name of some resource with a different UUID and also shouldn't


  		




  82
  82
  
    
	    // change in-between versions of the same resource, although


  		




  83
  83
  
    
	    // exceptions to both rules might be considered. Long name is


  		




  84
  84
  
    
	    // allowed to contain arbitrary unicode characters (within reason!).


  		




  ......




  95
  95
  
    
	    // the same.


  		




  96
  96
  
    
	    // Different versions (e.g. 1.0 and 1.3) of the same resource can be


  		




  97
  97
  
    
	    // defined in separate index.json files. This makes it easy to


  		




  98
  
  
    
	    // accidently cause an identifier clash. To help detect it, we


  		




  99
  
  
    
	    // require that each resource has a uuid associated with it. Attempt


  		




  100
  
  
    
	    // to define multiple resources with the same identifier and


  		




  101
  
  
    
	    // different uuids will result in an error being reported. Defining


  		




  102
  
  
    
	    // multiple resources with different identifiers and the same uuid


  		




  103
  
  
    
	    // is disallowed for now (it may be later permitted if we consider


  		




  104
  
  
    
	    // it good for some use-case).


  		




  
  98
  
    
	    // accidently cause an identifier clash. To help detect it, we allow


  		




  
  99
  
    
	    // each resource to have a UUID associated with it. Attempt to


  		




  
  100
  
    
	    // define multiple resources with the same identifier and different


  		




  
  101
  
    
	    // UUIDs will result in an error being reported. Defining multiple


  		




  
  102
  
    
	    // resources with different identifiers and the same UUID is


  		




  
  103
  
    
	    // disallowed for now (it may be later permitted if we consider it


  		




  
  104
  
    
	    // good for some use-case).


  		




  
  105
  
    
	    // As of package source schema version 1.0, UUIDs are optional and


  		




  
  106
  
    
	    // can be omitted.


  		




  105
  107
  
    
	    "uuid": "a6754dcb-58d8-4b7a-a245-24fd7ad4cd68",


  		




  106
  108
  
    

  		




  107
  109
  
    
	    // Version should match the upstream version of the resource (e.g. a


  		




  ......




  157
  159
  
    
	    "identifier": "helloapple",


  		




  158
  160
  
    

  		




  159
  161
  
    
	    // "long name" and "uuid" have the same meaning as in the case of


  		




  160
  
  
    
	    // resources. Uuids of a resource and a mapping can technically be


  		




  161
  
  
    
	    // the same, but it is recommended to avoid even this kind of


  		




  162
  
  
    
	    // repetition.


  		




  
  162
  
    
	    // resources and "uuid" is also optional. UUIDs of a resource and a


  		




  
  163
  
    
	    // mapping can technically be the same but it is recommended to


  		




  
  164
  
    
	    // avoid even this kind of repetition.


  		




  163
  165
  
    
	    "long_name": "Hello Apple",


  		




  164
  166
  
    
	    "uuid": "54d23bba-472e-42f5-9194-eaa24c0e3ee7",


  		




  165
  167
  
    

  		












Also available in:  Unified diff