[Feature]: Static Schemas package

[wilwade]

Feature Description

Details

Always fetching the schema ids from the chain works, but usually it is not needed as the values are static.

Let's publish a package (suggested at @frequency-chain/schemas) that has the following:

• A way to get the schema id from the schema namespace, name, and version. (see below for example)
• A way to get the schema namespace, name, and version from the id
• Have zero dependencies
• Placed in the js/schemas folder
• Releases should be tagged only when the contents change, but this should still work to release at the same time as the node image with the mainnet schema included.
• Perhaps a generator to generate from the mainet schema data

// This has already applied the transformation from the v1.13.0 migration
export const SCHEMA_NAME_TO_ID = new Map<string, number>([
  ['dsnp.broadcast@v1', 2],
  ['dsnp.broadcast@v2', 17],
  ['dsnp.dsnp-content-attribute-set@v1', 12],
  ['dsnp.ext-content-attribute-set@v1', 13],
  ['dsnp.private-connections@v1', 10],
  ['dsnp.private-follows@v1', 9],
  ['dsnp.profile-resources@v1', 15],
  ['dsnp.profile@v1', 6],
  ['dsnp.public-follows@v1', 8],
  ['dsnp.public-key-assertion-method@v1', 14],
  ['dsnp.public-key-key-agreement@v1', 7],
  ['dsnp.reaction@v1', 4],
  ['dsnp.reply@v1', 3],
  ['dsnp.reply@v2', 18],
  ['dsnp.tombstone@v1', 1],
  ['dsnp.tombstone@v2', 16],
  ['dsnp.update@v1', 5],
  ['dsnp.update@v2', 19],
  ['dsnp.user-attribute-set@v1', 11],
  ['dsnp.user-attribute-set@v2', 20],
  ['frequency.default-token-address@v1', 21],
]);

Searched for Related Issues

• I have done a search for related issues and either found none, or noted them