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.

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

Unsupported logic #304

Closed
danielghost opened this issue Dec 11, 2023 · 1 comment · Fixed by #306
Closed

Unsupported logic #304

danielghost opened this issue Dec 11, 2023 · 1 comment · Fixed by #306
Assignees

Comments

@danielghost
Copy link
Contributor

In addition to the changes made for #302, the unsupported logic should change to check which child elements are supported, as per the spec:

datamodel.element._children
The _children keyword is used to determine all of the elements in a group or category that are supported by the LMS.

LMSGetValue(datamodel.group._children)
The return value is a comma-separated list of all of the element names in the specified group or category that are supported by the LMS. If an element has no children, but is supported, an empty string ("") is returned. An empty string ("") is also returned if an element is not supported. A subsequent request for last error [LMSGetLastError()] can determine if the element is not supported. The error “401 Not implemented error” indicates the element is not supported.

The current method of just checking _count could lead to errors being raised where not all the child elements are supported.

Copy link

🎉 This issue has been resolved in version 5.9.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant