Generating Change Query MetaEd Artifacts for Extensions
- Vinaya Mayya
ODS / API source code is already updated when you access the change query enhancements. However if you have extensions, extension artifacts need to be regenerated using a MetaEd dev release 3.0.2-dev.4.
To obtain 3.0.2-dev.4 dev release version: Navigate to your MetaEd IDE installation directory and enter:
yarn upgrade atom-metaed@3.0.2-dev.4
To target MetaEd for ODS/API v5.3 extension and generate artifacts for change query enhancements, you will need to use metaed-console command line runner that targets API 6.0 while using DS 3.3.1b. The attached sample configuration file in the downloads section can be used. Update the configuration file per your need:
| Setting Name | Sample Value | Description |
|---|---|---|
| artifactDirectory | C:\\MetaEd\\MetaEdOutput | Generated outputs will be found in this directory |
| projects | - | Is an array of MetaEd project information, taken from the package.json of those MetaEd projects. Core is always first. Extensions follow and are optional. |
| projects:projectName | SampleStudentTranscript | ProjectName taken from package.json of the MetaEd project |
| projects:namespaceName | SampleStudentTranscript | Same as projectName, except for EdFi |
| projects:projectExtension | EXTENSION | Is always empty for core and "EXTENSION" for extensions. |
| projectPaths | C:\\MetaEd\\StudentTranscriptMetaEd | Is an array of the directory paths to each project, in the same order as "projects" |
| defaultPluginTechVersion | 6.0.0 | Is the API version to target. Must be 6.0.0 for this use case. |
On the command line navigate to node_modules\@edfi\metaed-console\dist folder in your MetaEd IDE installation directory and run:
node index.js --config <config-filename>
The following link contains the Visual Studio Extension:
MetaEdConfig-API-5.3-DS-3.3.1b.json