-
Notifications
You must be signed in to change notification settings - Fork 121
Conversation
Otherwise element.scrollIntoView() could be called on the item (via ActiveItemMixin) while it was hidden or at (0, 0), causing the browser to scroll to the top of the page when the dropdown was opened. PiperOrigin-RevId: 179624999
PiperOrigin-RevId: 179704935
PiperOrigin-RevId: 179710605
Based on feedback from external sync #203 PiperOrigin-RevId: 179729861
PiperOrigin-RevId: 179735522
…Move the initialization of the component into ngChanges so that if the componentFactory, and the value both change in the same turn the component will be initialized with the correct value right away. PiperOrigin-RevId: 179756891
It took me about half an hour to figure this one out, so this short comment might save the next person some time. PiperOrigin-RevId: 179785103
PiperOrigin-RevId: 179819717
PiperOrigin-RevId: 179858020
…n auto select and dropdown select components. PiperOrigin-RevId: 179943921
PiperOrigin-RevId: 180303717
PiperOrigin-RevId: 180601492
PiperOrigin-RevId: 180768448
PiperOrigin-RevId: 180886341
This is to prepare for the new language restriction: dart-lang/sdk#30326 PiperOrigin-RevId: 180941194
PiperOrigin-RevId: 180971363
This matches the styling of disabled <material-checkbox>. Update disabled .label-description to match; remove manual styling that was making the text lighter. PiperOrigin-RevId: 180978929
Add exclusion for unused file. Update CHANGELOG.md, README.md with notes. Bump dependency versions. PiperOrigin-RevId: 181244068
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
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. There is only one minor comment about repeated link definitions in markdown. Also, I haven't tried out the new build process (I'll do that a little later).
is evolving. We expect to no longer require overrides once we are at a beta | ||
release, but this is unlikely until sometime in early 2018. | ||
|
||
[dep_overrides]: https://www.dartlang.org/tools/pub/dependencies#dependency-overrides |
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.
Minor: rather than repeat this link definition (which also appears on L19), it might be preferable to include it only once at the end of the file.
Status: waiting for sass_builder update to be published. dart-league/sass_builder#17 |
This was for AngularDart v1. PiperOrigin-RevId: 181273259
This allows replacing this client template: <material-tab-strip [activeTabIndex]="activeTabIndex" (tabChange)="onTabChange($event)"> with this slightly more idiomatic client template: <material-tab-strip [(activeTabIndex)]="activeTabIndex"> PiperOrigin-RevId: 181340697
…enderer is used. PiperOrigin-RevId: 181342963
…n it closes. Current behavior: - If filter is inside popup, doesn't focus on open or close. - If filter is not inside popup, focuses on both open and close. PiperOrigin-RevId: 181345927
PiperOrigin-RevId: 181372356
PiperOrigin-RevId: 181381258
Using dynamic as bottom will become an error in Dart 2.0. dart-lang/sdk#29630 PiperOrigin-RevId: 182020806
Previously there was no visual indicator that the input was invalid when this mixin was used. PiperOrigin-RevId: 182085196
…s size. PiperOrigin-RevId: 182269449
Fixes an issue where ActiveItemMixin would cause the entire page to scroll unnecessarily in Firefox. PiperOrigin-RevId: 182272488
… case. Follow up CL updates the tools cell to use new interface PiperOrigin-RevId: 182289314
PiperOrigin-RevId: 182346419
In Dart 2.0, assert will only accept booleans, not closures any more. The solution to upgrade is very simple: we just self-execute any closures passed to assert today. PiperOrigin-RevId: 182406596
Remove unused table_selection_model.dart file. Cleanup outdated Copybara transformations. Bump sass_builder dependency. PiperOrigin-RevId: 182441504
@chalin One more sync of changes in and now ready to publish. Travis is failing because of a pub <--> sdk dev.18 issue at the moment but you can test again with the example branch https://github.com/dart-lang/angular_components_example/tree/support-build-runner. |
Ok, will take a look first thing tomorrow! cc @kwalrath |
@@ -68,12 +51,39 @@ bool getBool(inputValue) { | |||
inputValue, 'inputValue', 'Expected a String, or bool type'); | |||
} | |||
|
|||
/// Parses html attribute [String] to a [bool]. |
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.
Nit: html --> HTML
/// | ||
/// Should be used to parse values passed to @Attribute constructor argument. | ||
/// | ||
/// This does not fully follow the HTML boolean attribute definition |
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.
This does not fully follow the HTML boolean attribute definition (https://stackoverflow.com/a/4139805)
"Does not fully follow" would mean that it supports a subset of the definition, but that in theory it could be extended/completed so that it does follow the full definition. This is not the case.
IMHO, this function is in conflict with the HTML boolean attribute definition, since it matches the HTML boolean attribute definition only for the case where the attribute value is an empty string, and it goes against the definition for other cases (where the value is "true" or "false", and it fails to recognize the case where the value matches the attribute name, ignoring case). In fact, this throws an error if the value matches the attribute name.
To make this clear, maybe this function should be named ngAttributeToBool()
to be in contrast with what might be named htmlAttributeToBool()
.
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.
@rkj Any thoughts on rewording the comments here for more clarity? We can update them in a future sync to github.
/// to false value. | ||
/// | ||
/// When no attribute is present [defaultValue] value is returned (by default | ||
/// false). |
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.
Nit: a default of the default :) ... I would keep this DRY and drop the "(by default false)" since this can be reckoned by reading the function signature.
if (inputValue == null) return defaultValue; | ||
return _parseBool(inputValue); | ||
} | ||
|
||
/// A typed version of [getDynamic]. | ||
/// | ||
/// If [inputValue] is an [int], returns it. | ||
/// If [inputValue] is a `null`, returns [defaultValue]. | ||
/// If [inputValue] is a String, parses using [onString], or uses [int.parse]. |
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.
There is no use of onString()
in the function body.
* Wait for the popup to be visible before activating dropdown items. | ||
* Stop escape keyboard events from propagating after they are handled. | ||
* Disallow deselection when clicked on a selected item with single selection | ||
* models. |
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.
* models.
--> models.
since it is a continuation from the previous bullet.
* Material Tree: Autofocus the filter when `MaterialTreeDropdown` is opened, | ||
but not when it closes. | ||
* Better support for the zippy expansion case in selection model. | ||
* Deprecate getBool, angular supports it now natively. |
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.
angular --> Angular
Btw, our convention in the docs is for method/function names to be followed by parentheses:
getBool
--> getBool()
.
* Add a feature detector for `position: sticky`. | ||
* Migrate from Glyph to Material Icon. | ||
* Remove unused table model. | ||
* Remove the getDynamic method from properties helpers. |
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.
getDynamic --> getDynamic()
* Remove uses of .runtimeType. | ||
* Fix uses_bottom_as_dynamic ("fuzzy arrow") errors. | ||
* Cleanup unneeded `preserveWhitespace: false` and `preserveWhitespace: true`. | ||
* Cleanup type warnings and other Dart 2.0 fixes. |
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.
Dart 2.0 --> Dart 2
@@ -12,6 +72,12 @@ dependency_overrides: | |||
analyzer: ^0.31.0-alpha.1 | |||
``` | |||
|
|||
This is because Angular is starting to use and support the Dart 2.0.0 SDK, which |
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.
Dart 2.0.0 --> Dart 2
if (inputValue == null) return defaultValue; | ||
return _parseBool(inputValue); | ||
} | ||
|
||
/// A typed version of [getDynamic]. |
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.
getDynamic()
has been removed from this file so the doc comment shouldn't refer to it.
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.
A few nits, but I do have one more significant concern about the doc comments for attributeToBool()
. None of it is gating, of course. Please see inlined comments.
@nshahan - FYI, our AngularDart example apps have been converted to use build_runner, and the apps using angular_components run just fine (e.g., as shown for the template-syntax example app in this Travis log). |
PiperOrigin-RevId: 182548382
…rning. Tested: https://test.corp.google.com/ui#id=OCL:182564188:BASE:182564721:1516390579043:eb6c9c65 Failures are flakes or already failing. PiperOrigin-RevId: 182584854
|
||
> NOTE: This code is considered production quality, but depends on angular: | ||
> 5.0.0-alpha+3. The alpha tag represents the evolving nature of the AngularDart | ||
> api, not code quality (5.0.0-alpha+3 is used in production Google apps). |
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.
The Angular version was bumped up (from +3 to +4) in the pubspec.yaml, just before merging. This changelog entry should be referring to 5.0.0-alpha+4.
Context: #208 (review) Not sure about renaming the method, I doubt we need the html version. PiperOrigin-RevId: 182801890
Context: #208 (review) Not sure about renaming the method, I doubt we need the html version. PiperOrigin-RevId: 182801890
Adds support for building with build_runner.
Sync recent changes for all components.
Can test new build process with https://github.com/dart-lang/angular_components_example/tree/support-build-runner