Getx: What purpose of using extension on Object?

[SHRJamal]

I checked code and found that you have an extension on object
extension ObjectExtension on Object { Rx<Object> get obs => Rx(this); }

I suggest to make it as generic, it makes more sense:
extension RxT<T> on T { Rx<T> get obs => Rx(this); }

[jonataslaw]

I checked code and found that you have an extension on object
extension ObjectExtension on Object { Rx<Object> get obs => Rx(this); }

I suggest to make it as generic, it makes more sense:
extension RxT<T> on T { Rx<T> get obs => Rx(this); }

I think there is no semantic difference between the two approaches.
Do you think it gets clearer with <T>?

I can't see any practical differences in this approach, but if it's more readable to other devs, I can change that.

[SHRJamal]

when you do .obs on non-primitive types, you lose the type.
for example user.obs gives Rx<Object>, It should be Rx<User> instead.
With the solution, I gave it will solve this.

[SHRJamal]

I also have some other suggestions on code cleaning and recommend to add effective-dart lint rules. so that we have common rules for future contributions.
I can make pull request if you want. I like this packages and would love to contribute.

[jonataslaw]

I was unable to reproduce this, but either way, I will consider it for the next update.

[SHRJamal]

Here it' s really doesn't, just think about it. that should not be allowed by dart anyway

[jonataslaw]

Dart behaving differently on different machines, lol.
Thank you for mentioning this, as it never happened on my side, it was never my concern, I am changing this and I will update it.

[Nipodemos]

don't know if it helps, but i am using Flutter 1.17.4 (stable channel) and it happens just like @SHRJamal showed.

[jonataslaw]

Changed on last version, thanks.