Return String should be nullable, no?

[kevmoo]

web/web/lib/src/dom/html.dart

Line 1281 in 6538aca

external String operator [](String name);

CC @srujzs

[srujzs]

This is similar to #181. The IDL claims the return type is non-nullable, but naturally it would be nice to coerce missing values to null instead of a cast failure. I'm not sure if the behavior is similar everywhere a getter is declared in the IDL to make that change. The current solution is using has to check for existence.

[rutvik110]

I'm not sure if the behavior is similar everywhere a getter is declared in the IDL to make that change. The current solution is using has to check for existence.

From what I observed in the idl specs, the behaviour isn't consistent. Some getters are non-nullable while some are defined nullable. I don't know yet what determines that though.

But it would be nice to make this nullable as the users won't have to remember to check for the nullable case by using has, it would be explicit by the returned value from the getter. I could contribute to this issue if you could share what changes we might be looking towards fixing this issue beside just making this getter nullable.