-
Notifications
You must be signed in to change notification settings - Fork 4
fix(typedoc): Fix merge properties from base classes and remove obsolete base class name rosolving. #175
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
Open
skrustev
wants to merge
7
commits into
master
Choose a base branch
from
skrastev/fix-base-props
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
fix(typedoc): Fix merge properties from base classes and remove obsolete base class name rosolving. #175
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
1e765b3
fix(typedoc): Fix merge properties from base classes and remove obsol…
skrustev 9a502fa
chore(*): Add a few more excluded interfaces from WC.
skrustev 05ce238
chore(*): Code tweaks and better checks
skrustev 4ee401b
refactor(typedoc): Use ts types.
skrustev 12b053b
chore(*): Remove extra check
skrustev 727014b
chore(*): Apply type to initializer
skrustev 16c8b36
chore: leftover comment
damyanpetev File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
And this list might need an update since the mixins deff have changed.
Would be better if we can just access the
ts.Typewith all resolved properties directly and just haveLitElement/HTMLElementas filter/cut-off point down the chain.Although, even that is not entirely true, since we do actually re-use some of the native props (think input name, focus/validity methods - not necessary re-declaring them). Not sure how many, but might want to figure out a way to highlight important ones if needed.
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.
So far these are only potentially problematic. Better than checking for props.