Repository navigation
Conversation
19a94b6 to
d390fdd
Compare
There was a problem hiding this comment.
Any idea why this property is of type true and not a boolean ?
d390fdd to
0b65882
Compare
6d3600c to
dd6fba6
Compare
|
No interest for this change ? =) |
|
This is a nice change conceptually. I just need to sit down and look over all the usage points. |
|
@dylhunn Should be really straight forward 😊 |
dd6fba6 to
3c1cee5
Compare
|
The presubmit is failing, any info on what is breaking ? |
06fffe3 to
b8d71f6
Compare
jessicajaniuk
left a comment
There was a problem hiding this comment.
reviewed-for: fw-animations
dylhunn
left a comment
There was a problem hiding this comment.
reviewed-for: fw-core, fw-forms
The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertion for example.
…operties. The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertions for example.
…perties. The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertions for example.
…roperties. The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertions for example.
…eadonly properties. The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertions for example.
…ly properties. The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of type assertions.
3226227 to
2da5233
Compare
|
g3 presubmit is passing. |
|
disabling pullapprove -- router change is a no-op |
|
This PR was merged into the repository by commit e5d327d. |
|
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. |
The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertion for example. PR Close angular#49754
…operties. (angular#49754) The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertions for example. PR Close angular#49754
…perties. (angular#49754) The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertions for example. PR Close angular#49754
…roperties. (angular#49754) The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertions for example. PR Close angular#49754
…eadonly properties. (angular#49754) The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of `any` type assertions for example. PR Close angular#49754
…ly properties. (angular#49754) The `Writable` type is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead of type assertions. PR Close angular#49754
The
Writabletype is usefull when we want overwrite readonly properties and we still want to maintain code navigation/reference. It should be use instead ofanyor{myPrivateKey: any}type assertions for example.See individual commits
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?