Skip to content

Commit 33e6fc5

Browse files
kyledavelaargrs
authored andcommitted
add option in typescript
1 parent 95ed6df commit 33e6fc5

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

typings/connection.d.ts

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ export interface ConnectionOptions extends EndpointOptions {
101101
* provided, it will be used in the `open` frame to let the peer know about the container id.
102102
* However, the associated container object would still be the same container object from
103103
* which the connection is being created.
104-
*
104+
*
105105
* The `"container_id"` is how the peer will identify the 'container' the connection is being
106106
* established from. The container in AMQP terminology is roughly analogous to a process.
107107
* Using a different container id on connections from the same process would cause the peer to
@@ -189,6 +189,10 @@ export interface ConnectionOptions extends EndpointOptions {
189189
* from peer should not prevent reconnect (by default this only includes `"amqp:connection:forced"`).
190190
*/
191191
non_fatal_errors?: string[];
192+
/**
193+
* @property {boolean} [all_errors_non_fatal] Determines if rhea's auto-reconnect should attempt reconnection on all fatal errors
194+
*/
195+
all_errors_non_fatal?: boolean,
192196
/**
193197
* @property {string} [key] The private key of the certificate to be used with tls connection option
194198
*/
@@ -376,7 +380,7 @@ export interface SenderOptions extends LinkOptions {
376380
autosettle?: boolean;
377381
/**
378382
* @property {object} target - The target to which messages are sent.
379-
*
383+
*
380384
* If the target is set to `{}` no target address will be associated with the sender; the peer
381385
* may use the `to` field on each individual message to handle it correctly in that case.
382386
* This is useful where maintaining or setting up a sender for each target address is
@@ -413,7 +417,7 @@ export interface MessageAnnotations {
413417
* Describes the delivery annotations. It is used for delivery-specific non-standard
414418
* properties at the head of the message. It conveys information from the sending
415419
* peer to the receiving peer. This is the base interface for Delivery Annotations.
416-
*
420+
*
417421
* @interface DeliveryAnnotations
418422
*/
419423
export interface DeliveryAnnotations {
@@ -521,7 +525,7 @@ export interface MessageHeader {
521525
* Describes the footer section. It is used for details about the message or delivery
522526
* which can only be calculated or evaluated once the whole bare message has been
523527
* constructed or seen (for example message hashes, HMACs, signatures and encryption details).
524-
*
528+
*
525529
* @interface MessageFooter
526530
*/
527531
export interface MessageFooter {

0 commit comments

Comments
 (0)