Project

General

Profile

« Previous | Next » 

Revision 48606f28

Added by koszko over 1 year ago

specify full schema URL in index.json

View differences:

index.json
24 24 

  		




  25
  25
  
    
// Unknown object properties will be ignored. This is for compatibility with


  		




  26
  26
  
    
// possible future revisions of the format.


  		




  27
  
  
    

  		




  28
  
  
    
// Various kinds of objects contain version information. Version is always an


  		




  29
  
  
    
// array of integers, with major version number being the first array item. When


  		




  30
  
  
    
// applicable, a version is accompanied by a revision field which contains a


  		




  31
  
  
    
// positive integer. If versions specified by arrays of different length need to


  		




  32
  
  
    
// be compared, the shorter array gets padded with zeroes on the right. This


  		




  33
  
  
    
// means that for example version 1.3 could be given as both [1, 3] and


  		




  34
  
  
    
// [1, 3, 0, 0] (aka 1.3.0.0) and either would mean the same.


  		




  35
  
  
    

  		




  36
  27
  
    
{


  		




  37
  28
  
    
    // Once our index.json schema changes, this field's value will change. Our


  		




  38
  29
  
    
    // software will be able to handle both current and older formats thanks to


  		




  39
  30
  
    
    // this information present in every index.json file. Schemas that differ by


  		




  40
  31
  
    
    // the first (major) number are always incompatible (e.g. a Hydrilla builder


  		




  41
  32
  
    
    // instance released at the time of 1.2 being the most recent schema version


  		




  42
  
  
    
    // will not understand version 2.0).


  		




  
  33
  
    
    // will not understand version 2.1).


  		




  43
  34
  
    
    // Schemas that are backwards-compatible will have the same major number


  		




  44
  35
  
    
    // and might differ by the second (minor) version number. The third (patch)


  		




  45
  36
  
    
    // and subsequent numbers are being ignored right now.


  		




  46
  
  
    
    "source_schema_version": [1],


  		




  
  37
  
    
    "$schema": "https://hydrilla.koszko.org/schemas/package_source-1.schema.json",


  		




  47
  38
  
    

  		




  48
  39
  
    
    // Used when referring to this source package. Should be consize, unique


  		




  49
  40
  
    
    // (among other source package names) and can only use a restricted set of


  		




  ......




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


  		




  94
  85
  
    
	    "long_name": "Hello Apple",


  		




  95
  86
  
    

  		




  
  87
  
    
	    // Item definitions contain version information. Version is


  		




  
  88
  
    
	    // represented as an array of integers, with major version number


  		




  
  89
  
    
	    // being the first array item. In case of resources, version is


  		




  
  90
  
    
	    // accompanied by a revision field which contains a positive


  		




  
  91
  
    
	    // integer. If versions specified by arrays of different length need


  		




  
  92
  
    
	    // to be compared, the shorter array gets padded with zeroes on the


  		




  
  93
  
    
	    // right. This means that for example version 1.3 could be given as


  		




  
  94
  
    
	    // both [1, 3] and [1, 3, 0, 0] (aka 1.3.0.0) and either would mean


  		




  
  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
  98
  
    
	    // accidently cause an identifier clash. To help detect it, we


  		












Also available in:  Unified diff