aep-dev / aep.dev

AEPs help developers and organizations build clear, consistent network APIs and clients by providing an extensible set of design guidelines.

http://aep.dev/

aep-dev/aep.dev Issues

Rename the repo?
Updated 21 days ago10
idea: adding a mega-example for OAS and linking to it, populating almost all examples.
Updated 23 days ago
All the AEP sidebar links lead to a 404
Closed 24 days ago2
pagination is missing an OpenAPI example
Updated 24 days ago
Long running operation AEP is incomplete/inconsistent
Updated 24 days ago3
proposal: upgrade openapi definitions to 3.1
Updated a month ago1
Add a diagram of the final tooling ecosystem
Updated 2 months ago
Propose a standard for OAS operationIDs.
Updated 3 months ago1
proto annotation for a method that supports partial update
Updated 3 months ago1
Proposal: use standard nouns instead of resource singular for field names standard patterns and methods.
Updated 3 months ago2
discuss the best PATCH semantic to update
Updated 3 months ago6
Create oneof AEP
Updated 3 months ago
adopt AIP-129 server-modified values and defaults.
Updated 4 months ago
Create annotations related to resource ID wildcard support when reading across collections
Updated 5 months ago2
AEP-0203: remove IDENTIFIER annotation.
Updated 6 months ago
AIP-200: add openapi example
Updated 6 months ago
OpenAPI extensions for AEP-0203 - field behavior
Updated 6 months ago
document must vs should usage
Updated 6 months ago
AIP-134: disallow partial responses
Updated 6 months ago
idea: make Update RPCs have a new proto field "path"
Updated 6 months ago
AIP-143: revisit the naming of "mime_type"
Updated 6 months ago
AEP-154: proposal: only support one etag type.
Updated 6 months ago
Consider removing `allow_missing` in update requests in favor of Apply/PUT
Updated 6 months ago
pagination: consider re-adding guidance on pagination token
Updated 6 months ago
AEP-155 not visible on aep.dev
Updated 6 months ago
Should this be a versioned reference?
Updated 6 months ago3
AEP-181: consider requiring beta components must set a time to achieve production.
Updated 7 months ago
AEP-181: consider formalizing governance of APIs
Updated 7 months ago
Move field behavior standard method behavior to standard methods
Updated 7 months ago
What does it mean to be self-contained? I think it suggests that you must consider carefully how you manage the protos and leverage shared definitions. But OpenAPI is more relaxed, and it is possible that your document is a description not a definition.
Updated 7 months ago
Adopt AEP-130: methods
Closed 7 months ago
Adopt AIP-202: fields
Updated 7 months ago
Adopt AIP-0156 Singleton resources
Closed 8 months ago1
AIP-124: clarify wording on metadata
Updated 8 months ago
[standard-fields] Improve distinction between `title` and `display_name` (or consider removing `title`)
Updated 8 months ago
Make examples in standard method AEPs consistent (esp. re HTTP/2 examples).
Updated 8 months ago1
AIP-136: "sort of work" is ambiguous
Updated 8 months ago1
AIP:-143: how to consider version of the tzdb used? `google.type.Date` handles this with an optional field for the tzdb version.
Updated 8 months ago
figure out how to reference the aep types repository
Updated 8 months ago
Make AEP-8: Style Guide prescribe casing for more than just field names
Updated 8 months ago
Consider saying that custom methods **should** use GET or POST.
Updated 8 months ago
chore: Normalize all guidance lists below examples
Updated 8 months ago
Use slugs rather than numbers in the AEPs
Updated 8 months ago
Pattern to replace soft-delete
Updated 8 months ago1
Apply Standard method
Updated 8 months ago1
Revisit whether AEP-CREATE should guide that create methods **should** be strongly consistent.
Updated 8 months ago
AIP-134: author an OAS example.
Updated 8 months ago
AIP-136: write an OAS example for resource-based custom methods.
Updated 8 months ago
Consider adding guidance about custom methods that "mirror" standard methods.
Updated 8 months ago
Discuss management plane vs declarative friendly
Updated 8 months ago