Opened 6 years ago

Last modified 6 years ago

#1491 accepted task

APIs using Properties may ignore defaults

Reported by: zzz Owned by: zzz
Priority: maintenance Milestone: 0.9.20
Component: api/general Version: 0.9.18
Keywords: easy Cc:
Parent Tickets: Sensitive: no


Our APIs that take a Properties argument may ignore defaults in those Properties, apparently because we iterate through the underlying Hashtable's entry set to copy the entries.

While less efficient, we must apparently use propertyNames() or stringPropertyNames() to get the defaults. Either that, or document that defaults are ignored.

Review at least core, router, streaming, and i2ptunnel.




Change History (1)

comment:1 Changed 6 years ago by zzz

Owner: set to zzz
Status: newaccepted

Most client-side APIs fixed and/or documented in 3eaeeefa714a4e792340915187e4f53aef886034 0.9.18-15-rc.

Leaving open for Router, RouterContext?, I2PAppContext, I2NP, …

Note: See TracTickets for help on using tickets.