Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat(editors/ied): add DO elements to IED editor #454
feat(editors/ied): add DO elements to IED editor #454
Changes from 6 commits
f5423a7
5f225b4
bcd4825
804a087
649b4b6
906d3c1
99e7b2a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do you see something speaking against using js getters to access these as properties? It may fit better with the rest of the codebase.
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.
I also would suggest that. You can also combine getNestedDOElement and getDOType to something like
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.
I agree with the removal of getDOType, because it's only usage is in getNestedDOElements :) So I will merge them!
I was wondering how you guys would implement it as a getter (the getNestedDOElements for example).
I think getters and setters should apply to properties, so you can control the access of a certain property. That's why I'm a bit confused about how it's being used right now in open-scd, for example in the voltage-level-editor.ts, I see a
get voltage()
without a property (the voltage method itself is handled as a property). In my opinion this is a wrong usage, but maybe my Typescript expertise is lacking here :)Is this how we want to use it and how we want this getNestedDOElements as well? :) If so, maybe we can discuss it!
This file was deleted.