Security News
Fluent Assertions Faces Backlash After Abandoning Open Source Licensing
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
@azure-tools/typespec-apiview
Advanced tools
Library for emitting APIView token files from TypeSpec
This package provides the TypeSpec emitter to produce APIView token file output from TypeSpec source.
Add @azure-tools/typespec-apiview
to your package.json
and run npm install
.
tsp compile {path to typespec project} --emit=@azure-tools/typespec-apiview
Add the following to the typespec-project.yaml
file.
emitters:
@azure-tools/typespec-apiview: true
For configuration see options
typespec-apiview
emitter.typespec-apiview
emitter.Currently there are no APIView-specific decorators...
Emitter options can be configured via the tspconfig.yaml
configuration:
emitters:
'@azure-tools/typespec-apiview':
<optionName>: <value>
# For example
emitters:
'@azure-tools/typespec-apiview':
output-file: my-custom-apiview.json
or via the command line with
--option "@azure-tools/typespec-apiview.<optionName>=<value>"
# For example
--option "@azure-tools/typespec-apiview.output-file=my-custom-apiview.json"
emitter-output-dir
Configure the name of the output directory. Default is tsc-output/@azure-tools/typespec-apiview
.
include-global-namespace
Normally, APIView will filter all namespaces and only output those in the service namespace and any
subnamespaces. This is to filter out types that come from the TypeSpec compiler and supporting libraries.
This setting, if true
, tells APIView to output the contents of the global (empty) namespace, which
would normally be excluded.
service
Filter output to a single service definition. If omitted, all service defintions will be output as separate APIView token files.
output-file
Configure the name of the output JSON token file relative to the output-dir
. For multi-service
specs, this option cannot be supplied unless the service
option is also set. If outputting
all services in a multi-service spec, the output filename will be the service root namespace with the
-apiview.json
suffix. Otherwise, the default is apiview.json
.
version
For multi-versioned TypeSpec, this parameter is used to control which version to emit. This
is not required for single-version specs. For multi-versioned specs, the unprojected TypeSpec will
be rendered if this is not supplied. For multi-service specs, this option cannot be supplied
unless the service
option is also set.
FAQs
Library for emitting APIView token files from TypeSpec
The npm package @azure-tools/typespec-apiview receives a total of 25,000 weekly downloads. As such, @azure-tools/typespec-apiview popularity was classified as popular.
We found that @azure-tools/typespec-apiview demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.