-
**Is your feature request related to a problem? Please describe.**
Is there currently a way to get type safety when calling `Toast.show` with a custom component. I want to enforce the correct prop…
-
# Info
Currently there is no type safety with Angular. We ask people to implement `CUSTOM_ELEMENTS_SCHEMA` when they import our packages. By doing this, it disables type safety for their application,…
-
## Problem
In this code, `myNumber` has type `number`, when its runtime value is actually `undefined`:
```ts
const numbers = [3, 5, 7, 11, 13];
const myNumber = numbers[100];
```
This can lead to b…
-
Remove the warning suppressing comments also.
-
Hey I'm having an issue with type safety when using $ helper.
Seems like when using $ helper, we lost full type safety since TS does not complain about "inexistentProp".
 |
| Status | NEW |
| Importance | P3 normal |
| Reported | Jan 26, 2017 03:45 EDT |
| Modified | Jan…
-
I noticed while looking at TodoMVC that the following isn't fully typesafe,
```typescript
return accumCombine(
[
[prependItemS, (item, list) => [item].concat(list)],
[
…
-
currently all of the interfaces are implemented as traits on Id. This means there's no type safety between objects. We should probably use something like the foreign_obj_type! macro from https://githu…
-
The [`IntoBytes` implementation](https://google.github.io/comprehensive-rust/unsafe-rust/unsafe-traits.html) is incorrect, as shown when running this program under Miri. The correct syntax is `&raw co…
-
### Which packages are impacted by your issue?
_No response_
### Describe the bug
Going to the article on how to use mappers linked from the documentation is pretty useless at the moment.
All the …