Hashtable React Native Reference Documentation

Hashtable

Current Version: 11.6.1

Chilkat.Hashtable

Store, look up, remove, enumerate, import, and serialize key/value pairs.

Chilkat.Hashtable provides a simple key/value collection for storing string and integer values by key. It can add or replace entries, look up values, test whether keys exist, remove entries, count items, enumerate keys, import URL query parameters, serialize values back to a query string, and save or load the table in XML format.

String and integer values

Store values as strings or integers using straightforward add, replace, and lookup methods.

Fast key lookup

Check whether a key exists and retrieve its value without manually scanning a list or parsing text.

Add, replace, and remove

Maintain a mutable collection by adding new entries, replacing existing values, removing individual keys, or clearing the table.

Enumerate keys

Retrieve the set of keys when application logic needs to loop through the stored entries.

Query string helpers

Import URL query parameters into the table and serialize the table back to a query-string representation.

XML persistence

Save the hashtable to XML or reload it from XML when values need to be persisted or transferred in a simple structured format.

Common pattern: Use Hashtable when application code needs a small mutable key/value table, especially for lookup tables, parsed query parameters, or simple string/integer settings. Add values with AddStr or AddInt, retrieve them with LookupStr or LookupInt, and use XML or query-string methods when the table needs to be saved, loaded, or converted.

Object Creation

// npm install @chilkat/react-native react-native-nitro-modules
// (React Native 0.76+ with the New Architecture; then `pod install` for iOS.  The Chilkat
//  native library is downloaded and verified during the native build -- see the package README.)

import { Chilkat, Hashtable } from '@chilkat/react-native'

// Once per app start, before any other Chilkat call:
Chilkat.unlockBundle('Anything for 30-day trial')   // shorthand for new Global().unlockBundle(..)

const hashtable = new Hashtable()
// ... the native object is released when `hashtable` is garbage collected, or now with hashtable.dispose()
new Hashtable()

Creates the underlying native Chilkat object. Hashtable is a Nitro Module HybridObject: use it from the JavaScript thread only (it cannot be passed to a Worklet or another runtime). Every member is synchronous and blocks the JavaScript thread until Chilkat returns; a method that can take a while also exists as a ...Async twin returning a Promise, which runs the same call on a native worker thread so the UI keeps rendering. While such a call is pending, every other call on this object throws, except abort() and assigning onPercentDone / onProgressInfo.

dispose(): void

Releases the native object immediately instead of waiting for garbage collection (useful for a large BinData or an open socket). Calling it more than once is harmless; any other use of the object afterwards throws. An object with a pending ...Async call cannot be disposed until the promise settles.

Errors

A method that can fail throws a plain Error: a method whose only outcome is success or failure returns void and throws on failure; a method producing a string or an object returns it and throws where Chilkat would have returned null. The error's message is "Class.method(...): reason", where the reason is the last informative line of the object's lastErrorText, which holds the full Chilkat log of the failed call. A ...Async twin rejects its promise with the same Error instead of throwing. Properties never throw, and methods that answer a question (has..., is..., ...) return a plain boolean.

try {
  hashtable.someMethod(...)
} catch (e) {
  console.log((e as Error).message)   // Hashtable.someMethod(...): <reason>
  console.log(hashtable.lastErrorText)   // the full Chilkat log of the failed call
}

// The same call without blocking the JavaScript thread:
try {
  await hashtable.someMethodAsync(...)
} catch (e) {
  console.log((e as Error).message)   // Hashtable.someMethodAsync: <reason>
}

Properties

Count
// read-only
readonly count: number
Introduced in version 9.5.0.97

The number of entries currently stored in the hashtable.

Each key contributes one entry regardless of whether its value is a string or an integer. Adding a new key increases Count; replacing the value of an existing key does not. Removing an entry decreases it, and Clear resets it to 0.

top
DebugLogFilePath
// read/write
debugLogFilePath: string

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
LastErrorHtml
// read-only
readonly lastErrorHtml: string

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
// read-only
readonly lastErrorText: string

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
// read-only
readonly lastErrorXml: string

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastMethodSuccess
// read/write
lastMethodSuccess: boolean

Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
VerboseLogging
// read/write
verboseLogging: boolean

If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
// read-only
readonly version: string

Version of the component/library, such as "10.1.0"

More Information and Examples
top

Methods

AddFromXmlSb
addFromXmlSb(sbXml: StringBuilder): void
Introduced in version 9.5.0.64

Reads hashtable XML previously produced by ToXmlSb from the StringBuilder passed in sbXml and adds the entries to this table.

The operation merges with the existing table: keys not present in the XML remain, and an imported entry replaces the current value for the same key. Call Clear first when the XML should completely replace the current contents.

Returns true when the XML is parsed and imported successfully; otherwise returns false.

Returns normally on success; throws an Error on failure.

More Information and Examples
top
AddInt
addInt(key: string, value: number): void
Introduced in version 9.5.0.51

Adds an entry whose string key is key and whose value is the integer value. If the key already exists, its previous value is replaced.

Returns true when the entry is added or replaced. Returns false if the operation cannot be completed, such as because memory could not be allocated.

One entry per key: Adding the same key again replaces the existing value; it does not create a second entry. Replacing a value does not increase Count. Use LookupInt to retrieve an integer value.

Returns normally on success; throws an Error on failure.

top
AddQueryParams
addQueryParams(queryParams: string): void
Introduced in version 9.5.0.62

Parses URL query parameters from queryParams and adds them to the hashtable as string entries. Pass the query component in the following form:

field1=value1&field2=value2&field3=value3

Each value is expected to be URL encoded and is URL decoded before being stored. If an imported key already exists, its previous value is replaced. Returns true on success and false if the query parameters cannot be imported.

Repeated parameter names: A hashtable stores one value per key. It cannot preserve a query string containing several independent values with the same field name. Use a list-oriented parser when repeated names must remain distinct.

Returns normally on success; throws an Error on failure.

More Information and Examples
top
AddStr
addStr(key: string, value: string): void
Introduced in version 9.5.0.51

Adds an entry whose string key is key and whose value is the string value. If the key already exists, its previous value is replaced.

Returns true when the entry is added or replaced. Returns false if the operation cannot be completed, such as because memory could not be allocated.

One entry per key: Adding the same key again replaces the existing value; it does not create a second entry. Replacing a value does not increase Count. Use LookupStr to retrieve a string value.

Returns normally on success; throws an Error on failure.

top
Clear
clear(): void
Introduced in version 9.5.0.51

Removes every entry from the hashtable. After this call, Count is 0.

The current hash-table capacity is retained. To clear the entries and also select a different bucket capacity, call ClearWithNewCapacity.

top
ClearWithNewCapacity
clearWithNewCapacity(capacity: number): void
Introduced in version 9.5.0.51

Removes every entry and reinitializes the hashtable with capacity buckets. The initial default capacity of a new Hashtable object is 521.

Returns true on success and false if the table cannot be reinitialized.

TermMeaning
CountThe number of stored entries.
CapacityThe number of hash buckets, not a maximum entry count.
Performance note: More buckets can reduce collisions for a large table, but use more memory. Choosing roughly twice the expected number of entries and using a prime number are tuning guidelines, not correctness requirements.

Returns normally on success; throws an Error on failure.

top
Contains
contains(key: string): boolean
Introduced in version 9.5.0.51

Returns true if the hashtable contains the string key key; otherwise returns false. The result tests key existence regardless of the value stored for that key.

Useful before lookup: Call Contains when a lookup result could be ambiguous. For example, LookupInt returns 0 both for a missing key and for an entry whose value is actually zero.
top
ContainsIntKey
containsIntKey(key: number): boolean
Introduced in version 9.5.0.64

Returns true if the hashtable contains the integer key key; otherwise returns false.

Key type: This method accepts an integer key. It is distinct from Contains, which tests for a string key, and from AddInt, whose key is a string and whose value is an integer.
top
GetKeys
getKeys(strTable: StringTable): void
Introduced in version 9.5.0.62

Appends all hashtable key strings to the StringTable passed in strTable. Existing strings already contained in strTable are not cleared.

Returns true on success and false on failure.

Enumeration order: Hashtable keys may be returned in any order. Do not depend on insertion order or sorted order. Clear the destination StringTable first when it should contain only the current hashtable keys.

Returns normally on success; throws an Error on failure.

More Information and Examples
top
LookupInt
lookupInt(key: string): number
Introduced in version 9.5.0.51

Returns the integer value associated with the string key key. This method is intended for entries stored with AddInt.

If the key does not exist, the return value is 0.

Missing key versus zero: Because 0 is also a valid stored value, call Contains first when the application must distinguish a missing key from an entry containing zero.
top
LookupStr
lookupStr(key: string): string
Introduced in version 9.5.0.51

Returns the string value associated with the string key key. This method is intended for entries stored as strings, including entries added by AddStr or AddQueryParams.

Check lookup success: The representation of a failed string-returning call varies by programming language and may be null, Nothing, or an empty string. An empty string may also be a legitimate value. Use Contains or LastMethodSuccess when the distinction matters.

Throws an Error on failure (where the description says null is returned, the method throws instead).

top
Remove
remove(key: string): void
Introduced in version 9.5.0.51

Removes the entry whose string key is key.

  • Returns true if the key existed and the entry was removed.
  • Returns false if the key was not present.

A false result caused by an absent key is a normal lookup outcome, not an indication that the hashtable was damaged. Removing an existing entry decreases Count by one.

Returns normally on success; throws an Error on failure.

top
ToQueryString
toQueryString(): string
Introduced in version 9.5.0.92

Serializes the hashtable as a URL query string in the following form:

key1=value1&key2=value2&key3=value3

Each value is URL encoded. The returned string does not include a leading ?.

Important limitations: Key order is not defined, and a hashtable contains only one value per key. Therefore the output is not suitable when parameter order is significant or repeated field names must be preserved. In language bindings where string-return failure is ambiguous, check LastMethodSuccess.

Throws an Error on failure (where the description says null is returned, the method throws instead).

More Information and Examples
top
ToXmlSb
toXmlSb(sbXml: StringBuilder): void
Introduced in version 9.5.0.64

Serializes the current hashtable to Chilkat's hashtable XML format and appends the XML to the StringBuilder passed in sbXml. Existing content in the StringBuilder is preserved.

Returns true on success and false on failure. The generated XML can be loaded by AddFromXmlSb.

&lt;hashtable&gt;
  &lt;e&gt;&lt;k&gt;key&lt;/k&gt;&lt;v&gt;value&lt;/v&gt;&lt;/e&gt;
&lt;/hashtable&gt;
Ordering: Because hashtable enumeration order is not defined, do not rely on entries appearing in insertion order or use the serialized text as a canonical, byte-for-byte representation.

Returns normally on success; throws an Error on failure.

More Information and Examples
top