Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Adopt changes to UUri instance ID wildcard #186

Closed
sophokles73 opened this issue Aug 13, 2024 · 1 comment
Closed

Adopt changes to UUri instance ID wildcard #186

sophokles73 opened this issue Aug 13, 2024 · 1 comment
Assignees
@sophokles73
Labels
breaking change This pull request introduces a change to public API which is not backwards compatible
Milestone
Spec level 1.6.0....

Comments

@sophokles73
Copy link
Contributor

sophokles73 commented Aug 13, 2024 •
edited
Loading

The uProtocol UUri specification has been changed to use 0xFFFF as the wildcard for a service's instance ID instead of 0x0000.

up-rust needs to be adapted accordingly once up-spec 1.6.0-alpha.4 has been released.
@sophokles73 sophokles73 added the breaking change This pull request introduces a change to public API which is not backwards compatible label Aug 13, 2024
@sophokles73 sophokles73 self-assigned this Aug 13, 2024
sophokles73 added a commit to SoftwareDefinedVehicle/uprotocol-sdk-rust_fork that referenced this issue Nov 12, 2024
@sophokles73
[eclipse-uprotocol#186] Use FFFF as wildcard pattern for uEntity inst…
e2750f9 
…ance ID

UUri has been changed to use FFFF as the pattern for matching any
entity instance.
@sophokles73 sophokles73 mentioned this issue Nov 12, 2024
Merged
sophokles73 added a commit that referenced this issue Nov 12, 2024
@sophokles73
[#186] Use FFFF as wildcard pattern for uEntity instance ID
9a816e0 
UUri has been changed to use FFFF as the pattern for matching any
entity instance.
@sophokles73
Copy link
Contributor Author

closed via #211

@sophokles73 sophokles73 added this to the alpha.4 milestone Nov 12, 2024
@PLeVasseur PLeVasseur mentioned this issue Nov 12, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sophokles73 sophokles73

Labels
breaking change This pull request introduces a change to public API which is not backwards compatible
Projects
None yet
Milestone
Spec level 1.6.0.alpha.4
Development

No branches or pull requests
1 participant
@sophokles73