Assigned
Status Update
No update yet.
Comments
vi...@google.com
Surely this is something that the developer can handle themselves. If they just have a reference to the Marker then add a custom property to the marker and use that as the id, I don't think we need to start adding more info to Marker objects for everyone.
I would need more use cases where this is out of the developers hands before I would consider putting this in the API.
I would need more use cases where this is out of the developers hands before I would consider putting this in the API.
vi...@google.com
If there was a property name that was guaranteed to be safe - then sure. Theoretically any property name longer than three characters won't conflict with a closure-compiler renamed property, but this could break things:
myMarker.a = "test".
This would also be fixable by having a sub-property for objects that was designated for developers to add to.
myMarker.a = "test".
This would also be fixable by having a sub-property for objects that was designated for developers to add to.
Description
I am currently working with the new TetheringManager introduced in Android Baklava, and I have noticed that the SoftApConfiguration API lacks essential Wi-Fi configuration options. Specifically, it does not provide the ability to set the SSID, password, and other critical settings required for a proper hotspot configuration.
Given that the TetheringManager is intended to replace the previous tethering API, it would be beneficial if SoftApConfiguration allowed for full customization of the Wi-Fi access point.
Could you please confirm whether this is an intended limitation or if there are plans to enhance the API to include these missing configuration options?
Thank you for your time and assistance.
Best regards,
David