-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
[items & things] Add toString
overrides & Clean-Ups
#198
Conversation
Signed-off-by: Florian Hotze <florianh_dev@icloud.com>
Signed-off-by: Florian Hotze <florianh_dev@icloud.com>
They were exported but undocumented so no one should have been using them and they are really advanced functionality. Signed-off-by: Florian Hotze <florianh_dev@icloud.com>
@jpg0 Can I remove thing builder and channel builder here? |
Signed-off-by: Florian Hotze <florianh_dev@icloud.com>
toString
overrides & Clean-UpstoString
overrides & Clean-Ups
Are they used? I don't mind whether they go or stay, I suppose it depends on the purpose of the library. I used them to define and register things and channels in scripts (and then refer to them from other scripts). I did this to move all my configuration into JS, and then could reference everything via JS imports instead of name strings. However if this library is limited to rules based on existing definitions, then this functionality should be removed. Maybe @digitaldan has an opinion? |
I would error on the side of simplicity. Since it's undocumented and probably unused by most, i think removing it makes sense. |
So we agree that we remove that? Can one of you please review here (although the changes apart from the removal are minimal). |
@jpg0 @digitaldan Can you please review here? You can ignore the |
Signed-off-by: Florian Hotze <florianh_dev@icloud.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Reference #197 (fixes the JS library side).
To Dos