Skip to content

fix formatting issue in AIP-2718 #1407

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
noahdietz merged 5 commits into from
Mar 18, 2025
Merged

fix formatting issue in AIP-2718 #1407

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
2cf4c2f
fix formatting issue in AIP-2718
bshaffer Aug 19, 2024
dab2915
Update 2718.md
bshaffer Aug 19, 2024
0a77afa
Merge branch 'master' into bshaffer-patch-1
noahdietz Jan 14, 2025
b303f72
Merge branch 'master' into bshaffer-patch-1
noahdietz Mar 14, 2025
e8a6f2c
Merge branch 'master' into bshaffer-patch-1
noahdietz Mar 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion aip/apps/2718.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ with One Platform or not.
For compliant references, you **should** avoid the use of the terms "reference"
and "name" in the field name. That is, `koala` is preferred to
`koala_reference` or `koala_name`
([see AIP-122](../0122.md#fields-representing-another-resource)).
(see [AIP-122][]).

For other target APIs, you **should** echo that API's terminology in the name
for clarity. For example, if the target API's `GetKoalaDataRequest` has a
Expand Down