Skip to content
This repository was archived by the owner on Mar 27, 2024. It is now read-only.

Destination device address#101

Merged
tlaukkan merged 2 commits into
tlaukkan:masterfrom
cdjackson:destination_device_address
Dec 4, 2016
Merged

Destination device address#101
tlaukkan merged 2 commits into
tlaukkan:masterfrom
cdjackson:destination_device_address

Conversation

@cdjackson

@cdjackson cdjackson commented Aug 29, 2016

Copy link
Copy Markdown
Collaborator

This is an updated version of #95. I've now updated the doc and removed commented code.

This changes the ZigBeeDestination to ZigBeeAddress, and then has two address classes - ZigBeeGroupAddress, and ZigBeeDeviceAddress. ZigBeeDevice no longer extends ZigBeeDestination - nothing relied on this extension, and it seems much better not to have this link.

It also makes ZigBeeAddress abstract, and then move the isGroup method into the implementation classes rather than having the parent class check for subclasses to see if it's a group which doesn't seem nice.

In general, everywhere where we had a network address and endpoint, I'm now using the address. It likely needs a bit more work, but I'd welcome your thoughts on wether or not you're happy with this approach.

Signed-off-by: Chris Jackson <[email protected]>
@cdjackson cdjackson force-pushed the destination_device_address branch 4 times, most recently from e38c3d6 to 776eb17 Compare August 29, 2016 21:42
@cdealti

cdealti commented Aug 30, 2016

Copy link
Copy Markdown
Collaborator

Hi guys I'm receiving tons of emails from Codacy with the following subject:
Re: [tlaukkan/zigbee4java] Destination device address (#101)
Is there a way to disable them without muting the thread?

@cdjackson cdjackson force-pushed the destination_device_address branch from 776eb17 to d210416 Compare August 30, 2016 16:03
@tlaukkan tlaukkan merged commit 68f9657 into tlaukkan:master Dec 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants