You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating the vsix package of an ADO extension, the CLI warns that .woff2 is missing a content type. It looks like this should be added in VsixManifestBuilder.CONTENT_TYPE_MAP, likely mapped to font/woff2.
> npx tfx extension create --manifests azure-devops-extension-dev.json --no-color
TFS Cross Platform Command Line Interface v0.17.0
Copyright Microsoft Corporation
warning: Could not determine content type for extension .woff2. Defaulting to application/octet-stream. To override this, add a contentType property to this file entry in the manifest.
The warning asks to set the contentType property in the files section but it does not seem that wildcards can be used there.
The text was updated successfully, but these errors were encountered:
When creating the vsix package of an ADO extension, the CLI warns that .woff2 is missing a content type. It looks like this should be added in
VsixManifestBuilder.CONTENT_TYPE_MAP
, likely mapped tofont/woff2
.The warning asks to set the
contentType
property in thefiles
section but it does not seem that wildcards can be used there.The text was updated successfully, but these errors were encountered: