@@ -194,6 +194,15 @@ <h2> Attributes</h2>
194
194
< a id ="att-nav "> </ a >
195
195
< div class ='table-title ' id ="nav-bar-colors "> Navigation bar settings (only applicable in read-mode)</ div >
196
196
< table class ="m-table ">
197
+ < tr >
198
+ < td class =" attr-col mono bold right "> use-path-in-nav-bar </ td >
199
+ < td class ="gray ">
200
+ < span class ='bold dark-gray '> Allowed:< span class ='blue '> true | false</ span > </ span >
201
+ set true to show API paths in the navigation bar instead of summary/description
202
+ </ td >
203
+ < td class ='default-col '> false</ td >
204
+ </ tr >
205
+
197
206
< tr >
198
207
< td class =" attr-col mono bold right "> nav-bg-color </ td >
199
208
< td class ="gray "> Navigation bar's background color </ td >
@@ -404,44 +413,58 @@ <h2> Attributes</h2>
404
413
< div class ='table-title ' id ='api-servers '> API Server</ div >
405
414
< table class ="m-table ">
406
415
< tr >
407
- < td class ="attr-col mono bold right "> api-key-name</ td >
408
- < td class ="gray "> Name of the API key that will be send while trying out the APIs</ td >
409
- < td class ='default-col '> Authorization</ td >
416
+ < td class ="mono bold right "> server-url</ td >
417
+ < td class ="gray ">
418
+ OpenAPI spec has a provision for providing the server url. The UI will list all the server URLs provided in the spec.
419
+ The user can then select one URL to which he or she intends to send API calls while trying out the apis.
420
+ However, if you want to provide an API server of your own which is not listed in the spec, you can use this property to provide one.
421
+ It is helpful in the cases where the same spec is shared between multiple environment say Dev and Test and each have their own API server.
422
+ </ td >
423
+ < td > (empty)</ td >
410
424
</ tr >
411
425
< tr >
412
- < td class ="mono bold right "> api-key-value </ td >
426
+ < td class ="mono bold right "> default- api-server </ td >
413
427
< td class ="gray ">
414
- Value of the API key that will be send while trying out the APIs.
415
- This can also be provided/overwritten from UI.
428
+ If you have multiple api-server listed in the spec, use this attribute to select the default API server, where all the API calls will goto.
429
+ This can be changed later from the UI
416
430
</ td >
417
431
< td > (empty)</ td >
418
432
</ tr >
419
433
< tr >
420
- < td class ="mono bold right "> api-key-location</ td >
421
- < td class ="gray ">
422
- < span class ='bold dark-gray '> Allowed:< span class ='blue '> header, query</ span > </ span > -
423
- determines how you want to send the api-key.
434
+ < td colspan ="3 " style ="border-bottom-style:dashed; text-align: center; ">
435
+ < br />
436
+ When providing API key using RapiDoc element, make sure that you provide all the 3 attributes with some default values
437
+ < span class ="mono blue "> api-key-name, api-key-location & api-key-value</ span >
438
+ < br />
439
+ Set < span class ="mono blue "> api-key-value</ span > to "< span class ="mono blue "> -</ span > "
440
+ if you are unsure of its value, and like to fill in later using JavaScript
441
+ < br /> < br />
424
442
</ td >
425
- < td > header</ td >
443
+
444
+ </ tr >
445
+ < tr >
446
+ < td class ="attr-col mono bold right "> api-key-name</ td >
447
+ < td class ="gray "> Name of the API key that will be send while trying out the APIs</ td >
448
+ < td class ='default-col '> (empty)</ td >
426
449
</ tr >
427
450
< tr >
428
- < td class ="mono bold right "> server-url </ td >
451
+ < td class ="mono bold right "> api-key-location </ td >
429
452
< td class ="gray ">
430
- OpenAPI spec has a provision for providing the server url. The UI will list all the server URLs provided in the spec.
431
- The user can then select one URL to which he or she intends to send API calls while trying out the apis.
432
- However, if you want to provide an API server of your own which is not listed in the spec, you can use this property to provide one.
433
- It is helpful in the cases where the same spec is shared between multiple environment say Dev and Test and each have their own API server.
453
+ < span class ='bold dark-gray '> Allowed:< span class ='blue '> header, query</ span > </ span > -
454
+ determines how you want to send the api-key.
434
455
</ td >
435
456
< td > (empty)</ td >
436
457
</ tr >
437
458
< tr >
438
- < td class ="mono bold right "> default- api-server </ td >
459
+ < td class ="mono bold right "> api-key-value </ td >
439
460
< td class ="gray ">
440
- If you have multiple api-server listed in the spec, use this attribute to select the default API server, where all the API calls will goto.
441
- This can be changed later from the UI
461
+ Value of the API key that will be send while trying out the APIs.
462
+ This can also be provided/overwritten from UI.
442
463
</ td >
443
464
< td > (empty)</ td >
444
465
</ tr >
466
+
467
+
445
468
</ table >
446
469
447
470
</ div >
0 commit comments