Expose ADAFRUIT_COMPANY_ID and MANUFACTURING_DATA_ADT

[kevinjwalters]

_MANUFACTURING_DATA_ADT and _ADAFRUIT_COMPANY_ID are defined in

Adafruit_CircuitPython_BLE/adafruit_ble/advertising/adafruit.py

Lines 43 to 44 in 5d58457

	_MANUFACTURING_DATA_ADT = const(0xFF)
	_ADAFRUIT_COMPANY_ID = const(0x0822)

as 0xFF and 0x0822, respectively. The underscore prefix in conjunction with the use of const() (@dhalbert clarified this) makes them truly private and unusable from elsewhere.

These reference values would be useful to expose from somewhere in adafruit_ble library for other code which is creating packets, e.g.

• adafruit_ble_broadcastnet
• adafruit_ble_radio

These currently have their own local variables with these values.

[kevinjwalters]

I'm thinking of using sequence_number like the one used for AdafruitSensorMeasurement in https://github.com/adafruit/Adafruit_CircuitPython_BLE_BroadcastNet/blob/c6328d5c7edf8a99ff719c3b1798cb4111bab397/adafruit_ble_broadcastnet.py#L84-L85 - I have added a note to #79 (comment) about this too.

Does it make sense for its id number (0x0003) to be somewhere to allow developers to use it in custom Advertisement packets?

[tekktrik]

Resolved by PR #154!

[dhalbert]

In the PR, if you use one of these magic phrases, the issue will get linked and then closed when the PR is merged:
https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

[tekktrik]

Oh I didn't know that, thank you!!