-
Notifications
You must be signed in to change notification settings - Fork 408
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.
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
Resources with no defined operations MUST NOT be considered as executable #1441
Comments
Nope, this is a bug. |
I want to fix it. Where should I start looking for assigning label for this button? |
Just to be sure we are talking about |
If this is about {
"13": {
"id": 13,
"name": "Registration Priority Order",
"operations": "NONE",
"instancetype": "single",
"mandatory": false,
"type": "unsigned_integer",
"range": "",
"units": "",
"description": "The LwM2M Client sequences the LwM2M Server registrations in increasing order of this value. If this value is not defined, registration attempts to this server are not impacted by other server registrations."
}
} It seems that returning |
I've created a fix on opl/EXEButton. |
I also feel this is the best way. 🙂 You can create a PR. |
I've created a PR |
Fixed in |
Thx @Warmek 🙏 |
Question
Should resources with no defined operations be defined as executable in leshan server demo? For example, resource 13 in 1-1_1.xml don't have any operation defined but in leshan server demo it's displayed as executable.
The text was updated successfully, but these errors were encountered: