We initially avoided this because it's a lot of boilerplate to pass JS objects which match BroflakeOptions, WebRTCOptions, and EgressOptions and validate their structure. There was no need to write all that back when we were happy to use nearly everything in the default structures.
Today, though, things are changing. As of March 30, 2023, we're forcibly overriding 10 fields across those 3 configuration structures. It's probably time to clean this up.
The big brained approach: add JavaScript constructors to create JS counterparts to NewDefaultBroflakeOptions, NewDefaultWebRTCOptions, and NewDefaultEgressOptions.
We initially avoided this because it's a lot of boilerplate to pass JS objects which match
BroflakeOptions,WebRTCOptions, andEgressOptionsand validate their structure. There was no need to write all that back when we were happy to use nearly everything in the default structures.Today, though, things are changing. As of March 30, 2023, we're forcibly overriding 10 fields across those 3 configuration structures. It's probably time to clean this up.
The big brained approach: add JavaScript constructors to create JS counterparts to
NewDefaultBroflakeOptions,NewDefaultWebRTCOptions, andNewDefaultEgressOptions.