Skip to content
This repository has been archived by the owner on May 23, 2024. It is now read-only.

@api-vendortag #156

Merged
merged 1 commit into from
Mar 29, 2018
Merged

@api-vendortag #156

merged 1 commit into from
Mar 29, 2018

Conversation

erunion
Copy link
Owner

@erunion erunion commented Mar 29, 2018

This completely replaces the old concept of API capabilities with a new, more generalized and OAI-compatible @api-vendortag.

You write them exactly the same you did capabilities:

@api-vendorTag needs:someRequirement

…

@api-param:private status (enum, needs:someRequirement) - The status of the object.

You configure them the same way you would with <capabilities>, that's just now called <vendorTags>:

<vendorTags>
    <vendorTag name="needs:someRequirement" />
</vendorTags>

And using our generators, you can also filter on them the same way you would with the --capability argument, it's now just called --vendor_tag.

Resolves #148

@erunion erunion merged commit a6d2e78 into v4-dev Mar 29, 2018
@erunion erunion deleted the api-vendor-tag branch March 29, 2018 19:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant