rticommunity · alvinkrebs · Jul 9, 2024 · Dec 12, 2019 · Feb 10, 2020 · Feb 11, 2020
diff --git a/.gitattributes b/.gitattributes
@@ -0,0 +1 @@
+package-lock.json	binary
diff --git a/.gitignore b/.gitignore
@@ -53,3 +53,6 @@ docs/_build/
 # node.js dependencies 
 node_modules/
 
+# VSCode
+.vscode/
+
diff --git a/LICENSE.pdf b/LICENSE.pdf
diff --git a/README.md b/README.md
@@ -48,9 +48,9 @@ The dependency [ref](https://www.npmjs.com/package/ref) is shipped as source cod
 
 ## License
 
-RTI Connector for JavaScript and RTI Connector for Python are part of the Connext
-DDS Professional Package. If you have a valid license for the RTI Connext DDS
-Professional Package, such license shall govern your use of RTI Connector for
-Python and RTI Connector for JavaScript. All other use of this software shall
+RTI Connector for JavaScript is part of the Connext
+Professional Package. If you have a valid license for the RTI Connext
+Professional Package, such license shall govern your use of
+RTI Connector for JavaScript. All other use of this software shall
 be governed solely by the terms of RTI’s Software License for Non-Commercial
-Use #4040, included at the top level of the `Connector for Python repository
+Use #4040.
diff --git a/README.rst b/README.rst
@@ -70,10 +70,9 @@ source code and requires a C++11 compiler.
 License
 -------
 
-RTI Connector for JavaScript and RTI Connector for Python are part of
-the Connext DDS Professional Package. If you have a valid license for
-the RTI Connext DDS Professional Package, such license shall govern your
-use of RTI Connector for Python and RTI Connector for JavaScript. All
+RTI Connector for JavaScript is part of
+the Connext Professional Package. If you have a valid license for
+the RTI Connext Professional Package, such license shall govern your
+use of RTI Connector for JavaScript. All
 other use of this software shall be governed solely by the terms of
-RTI’s Software License for Non-Commercial Use #4040, included at the top
-level of the \`Connector for Python repository
+RTI’s Software License for Non-Commercial Use #4040.
diff --git a/ci_config.yaml b/ci_config.yaml
@@ -0,0 +1,5 @@
+node_versions:
+  - "18.19"
+  - "19.9.0"
+  - "20.11"
+publish_version: "20"
diff --git a/docs/conf.py b/docs/conf.py
@@ -17,12 +17,12 @@
 # -- Project information -----------------------------------------------------
 
 project = 'RTI Connector for JavaScript'
-copyright = '2022, Real-Time Innovations, Inc.'
+copyright = '2024, Real-Time Innovations, Inc.'
 author = 'Real-Time Innovations, Inc.'
 
 # The full version, including alpha/beta/rc tags
-release = '1.2.2'
-version = '1.2.2'
+release = '1.3.0'
+version = '1.3.0'
 
 master_doc = 'index'
 primary_domain = 'js'
@@ -145,7 +145,7 @@ def setup(app):
         master_doc,
         'rticonnectorforjavascript.tex',
         'RTI Connector for Javascript',
-        '2022, Real-Time Innovations, Inc.',
+        '2024, Real-Time Innovations, Inc.',
         'manual'
     ),
 ]

diff --git a/docs/configuration.rst b/docs/configuration.rst
@@ -12,7 +12,7 @@ and *DataWriters*, data types and quality of service.
     :align: center
 
 *Connector* uses the XML schema defined by RTI's
-`XML-Based Application Creation feature <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/xml_application_creation/index.htm>`__.
+`XML-Based Application Creation feature <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/xml_application_creation/index.htm>`__.
 
 .. hint::
     The *Connext DDS* C, C++, Java and .NET APIs can also load the same XML files
@@ -50,7 +50,7 @@ how they are exposed in the *Connector* API:
 
 .. hint::
 
-  For an example configuration file, see `ShapeExample.xml <https://github.com/rticommunity/rticonnextdds-connector-py/blob/master/examples/python/ShapeExample.xml>`__.
+  For an example configuration file, see `ShapeExample.xml <https://github.com/rticommunity/rticonnextdds-connector-js/blob/master/examples/nodejs/ShapeExample.xml>`__.
 
 Data types
 ~~~~~~~~~~
@@ -75,11 +75,11 @@ and ``shapesize``:
 Types are associated with *Topics*, as explained in the next section, :ref:`Domain Library`.
 
 .. hint::
-    You can define your types in IDL and convert them to XML with `rtiddsgen <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/code_generator/users_manual/index.htm>`__.
+    You can define your types in IDL and convert them to XML with `rtiddsgen <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/code_generator/users_manual/index.htm>`__.
     For example: ``rtiddsgen -convertToXml MyTypes.idl``
 
 For more information about defining types, see
-`Creating User Data Types with XML <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/Creating_User_Data_Types_with_Extensible.htm>`__
+`Creating User Data Types with XML <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/Creating_User_Data_Types_with_Extensible.htm>`__
 in the *Connext DDS Core Libraries User's Manual*.
 
 For more information about accessing the data samples, see :ref:`Accessing the data`.
@@ -89,10 +89,10 @@ Domain library
 
 A domain library is a collection of domains. A domain specifies:
 
-  * A `domain id <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/ChoosingDomainID.htm>`__.
+  * A `domain id <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/ChoosingDomainID.htm>`__.
   * A set of registered types (from a subset of the types in ``<types>``).
     A registered type can have a local name.
-  * A set of `topics <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/WorkingWithTopics.htm>`__,
+  * A set of `topics <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/WorkingWithTopics.htm>`__,
     which are used by *DataReaders* and *DataWriters*.
 
 .. code-block:: xml
@@ -106,7 +106,7 @@ A domain library is a collection of domains. A domain specifies:
     </domain_library>
 
 For more information about the format of a domain library, see
-`XML-Based Application Creation: Domain Library <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/DomainLibrary.htm>`__.
+`XML-Based Application Creation: Domain Library <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/DomainLibrary.htm>`__.
 
 Participant library
 ~~~~~~~~~~~~~~~~~~~
@@ -139,12 +139,12 @@ as described in :ref:`Reading data (Input)`.
     </domain_participant_library>
 
 For more information about the format of a participant library, see
-`XML-Based Application Creation: Participant Library <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/ParticipantLibrary.htm>`__.
+`XML-Based Application Creation: Participant Library <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/ParticipantLibrary.htm>`__.
 
 Quality of service
 ~~~~~~~~~~~~~~~~~~
 
-All DDS entities have an associated `quality of service (QoS) <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/QosPolicies.htm>`__.
+All DDS entities have an associated `quality of service (QoS) <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/QosPolicies.htm>`__.
 There are several ways to configure it.
 
 You can define a QoS profile and make it the default. The following example
@@ -230,12 +230,12 @@ profile is equivalent to *MyQosProfile* above:
     </qos_library>
 
 You can read more in the *RTI Connext DDS Core Libraries User's Manual*, 
-`Configuring QoS with XML <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/XMLConfiguration.htm>`__.
+`Configuring QoS with XML <https://community.rti.com/static/documentation/connext-dds/current/doc/manuals/connext_dds/html_files/RTI_ConnextDDS_CoreLibraries_UsersManual/index.htm#UsersManual/XMLConfiguration.htm>`__.
 
 Logging
 ^^^^^^^
 
-Logging can be configured as explained in `Configuring Logging via XML <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/Configuring_Logging_via_XML1.htm>`__.
+Logging can be configured as explained in `Configuring Logging via XML <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/Configuring_Logging_via_XML1.htm>`__.
 
 For example, to increase the logging verbosity from the default (ERROR) to
 WARNING, define a ``qos_profile`` with the attribute
@@ -249,4 +249,4 @@ WARNING, define a ``qos_profile`` with the attribute
                 <verbosity>WARNING</verbosity>
             </logging>
         </participant_factory_qos>
-    </qos_profile>
+    </qos_profile>
diff --git a/docs/connector.rst b/docs/connector.rst
@@ -22,7 +22,7 @@ To create a new :class:`Connector`, pass an XML file and a configuration name to
    const connector = new rti.Connector('MyParticipantLibrary::MyParticipant', 'ShapeExample.xml')
 
 The XML file defines your types, QoS profiles, and DDS Entities. *Connector*
-uses the XML schema of `RTI's XML-Based Application Creation <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/XMLTagsConfigEntities.htm>`__.
+uses the XML schema of `RTI's XML-Based Application Creation <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/XMLTagsConfigEntities.htm>`__.
 
 The previous code loads the ``<domain_participant>`` named *MyParticipant* in
 the ``<domain_participant_library>`` named *MyParticipantLibrary*, which is defined in the
@@ -42,7 +42,7 @@ When you create a :class:`Connector`, the DDS *DomainParticipant* that you selec
 and all of its contained entities (*Topics*, *Subscribers*, *DataReaders*,
 *Publishers*, *DataWriters*) are created.
 
-For more information about the DDS entities, see `Core Concepts <https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/PartCoreConcepts.htm>`__
+For more information about the DDS entities, see `Core Concepts <https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/users_manual/index.htm#users_manual/PartCoreConcepts.htm>`__
 in the *RTI Connext DDS Core Libraries User's Manual*.
 
 .. note::

diff --git a/docs/copyright_license.rst b/docs/copyright_license.rst
@@ -6,17 +6,17 @@
 Copyrights and License
 **********************
 
-© 2022 Real-Time Innovations, Inc. |br|
+© 2024 Real-Time Innovations, Inc. |br|
 All rights reserved.  |br|
 Printed in U.S.A. First printing.  |br|
-February 2022. |br|
+March 2024. |br|
 
 .. rubric:: License
 
-RTI Connector for JavaScript and RTI Connector for Python are part of the Connext
-DDS Professional Package. If you have a valid license for the RTI Connext DDS
-Professional Package, such license shall govern your use of RTI Connector for
-Python and RTI Connector for JavaScript. All other use of this software shall
+RTI Connector for JavaScript is part of the Connext
+Professional Package. If you have a valid license for the RTI Connext
+Professional Package, such license shall govern your use of
+RTI Connector for JavaScript. All other use of this software shall
 be governed solely by the terms of RTI’s Software License for Non-Commercial
 Use #4040, included at the top level of the `Connector for JavaScript repository
 <https://github.com/rticommunity/rticonnextdds-connector-js>`__.
@@ -90,9 +90,11 @@ Website: https://support.rti.com/ |br|
   * The source code of this software (from https://github.com/udp/json-parser) 
     is used to build the native libraries provided by *RTI Connector*.
 
+  * Version 1.1.0
+
   * License:
 
-    Copyright (C) 2012, 2013, 2014 James McLaughlin et al.  All rights reserved.
+    Copyright (C) 2012-2021 the json-parser authors  All rights reserved.
     https://github.com/udp/json-parser
 
     Redistribution and use in source and binary forms, with or without

diff --git a/docs/data.rst b/docs/data.rst
@@ -8,7 +8,7 @@ and arrays of primitive types or structs, etc.
 
 These types are defined in XML following the format of
 `RTI's XML-Based Application Creation feature
-<https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/XMLTagsConfigEntities.htm>`__.
+<https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/xml_application_creation/index.htm#xml_based_app_creation_guide/UnderstandingXMLBased/XMLTagsConfigEntities.htm>`__.
 
 To access the data, :class:`Instance` and :class:`SampleIterator` provide
 setters and getters that expect a ``fieldName`` string, used to identify 
@@ -239,6 +239,13 @@ then you must take the following into account.
   The :meth:`Instance.setNumber()` operation can safely handle ``abs(value) < 2^53``,
   whereas the :meth:`SampleIterator.getNumber()` operation can safely handle ``abs(value) <= 2^53``.
 
+.. note::
+
+  The use of "Infinity", "-Infinity" and "-0" has some potential pitfalls and is
+  not recommended. If your application must use these values, refer to
+  `this knowledge base article <https://community.rti.com/kb/advanced-data-access-using-connector-javascript>`__
+  for more information.
+
 Accessing structs
 ^^^^^^^^^^^^^^^^^
 
@@ -465,7 +472,7 @@ To clear a member, set it to ``null`` explicitly::
 
 For more information about optional members in DDS, see 
 `Optional Members 
-<https://community.rti.com/static/documentation/connext-dds/6.1.2/doc/manuals/connext_dds_professional/extensible_types_guide/index.htm#extensible_types/Optional_Members.htm>`__ 
+<https://community.rti.com/static/documentation/connext-dds/7.3.0/doc/manuals/connext_dds_professional/extensible_types_guide/index.htm#extensible_types/Optional_Members.htm>`__
 in the *Extensible Types Guide*.
 
 Accessing unions
@@ -539,4 +546,55 @@ The key fields can be accessed as follows:
 
 .. warning::
     When the sample has an instance state of ``'NOT_ALIVE_DISPOSED'`` only the
-    key fields should be accessed.
+    key fields should be accessed.
+
+Accessing key values of disposed samples
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Using :meth:`Output.write`, an :class:`Output` can write data, or dispose or 
+unregister an instance.
+Depending on which of these operations is performed, the ``instance_state`` of the
+received sample will be ``'ALIVE'``, ``'NOT_ALIVE_NO_WRITERS'`` or ``'NOT_ALIVE_DISPOSED'``.
+If the instance was disposed, this ``instance_state`` will be ``'NOT_ALIVE_DISPOSED'``.
+In this state, it is possible to access the key fields of the instance that was disposed.
+
+.. note::
+    :attr:`SampleInfo.valid_data` will be false when the :attr:`SampleInfo.instance_state`
+    is ``'NOT_ALIVE_DISPOSED'``. In this situation it's possible to access the
+    key fields in the received sample.
+
+The key fields can be accessed as follows:
+
+.. code-block::
+
+    // The output and input are using the following type:
+    // struct ShapeType {
+    //     @key string<128> color;
+    //     long x;
+    //     long y;
+    //     long shapesize;
+    // }
+
+    output.instance.set('x', 4)
+    output.instance.set('color', 'Green')
+    // Assume that some data associated with this instance has already been sent
+    output.write({ action: 'dispose' })
+    await input.wait()
+    input.take()
+    let sample = input.samples.get(0)
+
+    if (sample.info.get('instance_state') === 'NOT_ALIVE_DISPOSED') {
+        // sample.info.get('valid_data') will be false in this situation
+        // Only the key-fields should be accessed
+        let color = sample.get('color') // 'Green'
+        // The fields 'x','y' and 'shapesize' cannot be retrieved because they're
+        // not part of the key
+        // You can also call getJson() to get all of the key fields in a JSON object.
+        // Again, only the key fields returned within the JSON object should
+        // be used.
+        let keyValues = sample.getJson() // { color: 'Green', x: 0, y: 0, shapesize: 0 }
+    }
+
+.. warning::
+    When the sample has an instance state of ``'NOT_ALIVE_DISPOSED'`` only the
+    key fields should be accessed.