From ca3e64fb7eeac68dbdbc703bbf7934ae0a355919 Mon Sep 17 00:00:00 2001 From: seiya Date: Wed, 13 Feb 2019 22:58:27 +0900 Subject: [PATCH 1/2] fix a typo in the Security Filtering section --- versions/3.0.3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versions/3.0.3.md b/versions/3.0.3.md index 7920019331..1e22546357 100644 --- a/versions/3.0.3.md +++ b/versions/3.0.3.md @@ -3392,7 +3392,7 @@ While not part of the specification itself, certain libraries MAY choose to allo Two examples of this: 1. The [Paths Object](#pathsObject) MAY be empty. It may be counterintuitive, but this may tell the viewer that they got to the right place, but can't access any documentation. They'd still have access to the [Info Object](#infoObject) which may contain additional information regarding authentication. -2. The [Path Item Object](#pathItemObject) MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different than hiding the path itself from the [Paths Object](#pathsObject), so the user will not be aware of its existence. This allows the documentation provider to finely control what the viewer can see. +2. The [Path Item Object](#pathItemObject) MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different than hiding the path itself from the [Paths Object](#pathsObject), so the user will be aware of its existence. This allows the documentation provider to finely control what the viewer can see. ## Appendix A: Revision History From 254905de5838fca04d02b8847d86b4e14e3edf18 Mon Sep 17 00:00:00 2001 From: Mike Ralphson Date: Fri, 14 Feb 2020 13:44:54 +0000 Subject: [PATCH 2/2] Security filtering slight reword --- versions/3.0.3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versions/3.0.3.md b/versions/3.0.3.md index 1e22546357..00c09c8d60 100644 --- a/versions/3.0.3.md +++ b/versions/3.0.3.md @@ -3392,7 +3392,7 @@ While not part of the specification itself, certain libraries MAY choose to allo Two examples of this: 1. The [Paths Object](#pathsObject) MAY be empty. It may be counterintuitive, but this may tell the viewer that they got to the right place, but can't access any documentation. They'd still have access to the [Info Object](#infoObject) which may contain additional information regarding authentication. -2. The [Path Item Object](#pathItemObject) MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different than hiding the path itself from the [Paths Object](#pathsObject), so the user will be aware of its existence. This allows the documentation provider to finely control what the viewer can see. +2. The [Path Item Object](#pathItemObject) MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different from hiding the path itself from the [Paths Object](#pathsObject), because the user will be aware of its existence. This allows the documentation provider to finely control what the viewer can see. ## Appendix A: Revision History