[native_assets_cli] Syntax for assets_for_build and hooks/metadata
#2163
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug: #1251
This PR contains the JSON spec for:
MetadatawithAssets #2164For more details see that PR.
This PR adds the syntax for passing assets from build hooks to build hooks.
build output
assets_for_build:{ "assets": [], "assets_for_build": [ { "encoding": { "a_key": "some_value" }, "some_key": "some_value", "type": "some_asset_type" } ], "assets_for_linking": {}, }build input
assetsper package name:{ "assets": { "some_package": [ { "some_key": "some_value", "type": "some_asset_type" } ] }, "config": {}, }Secondly, this PR adds a syntax for metadata assets (assets that cannot be bundled but just ferry information between different hooks).
{ "encoding": { "key": "foo", "value": "bar" }, "type": "hooks/metadata" },The schemas now check these.
And this is covered by tests.
Changes to the generated schemas:
assetand build outputassets_for_buildwith theCodeAssetandDataAssetin the generated extension schemas.Notable changes to the syntax generator:
encoding) in the super class.Objectfields (used forMetadataAsset.value).