chore: remove accessor type workaround#7659
Merged
andrewseguin merged 1 commit intoOct 12, 2017
Merged
Conversation
googlebot
added
the
cla: yes
Due to angular/dgeni-packages#246 the Material docs package used a workaround for accessor types. The issue has been fixed with angular/dgeni-packages#247 and the workaround can be removed now.
devversion
force-pushed
the
chore/remove-accessor-type-workaround
branch
from
94e82a3 to
1f33503
Compare
Closed
jelbourn
added
pr: lgtm
action: merge
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Due to angular/dgeni-packages#246 the Material docs package used a workaround for accessor types.
The issue has been fixed with angular/dgeni-packages#247 and the workaround can be removed now.