Use of part of, should be avoided about flutter_janus_client HOT 4 CLOSED

this isn't that big library and earlier version of this library was written with export and imports but that architecture of api split across multiple files was having serious drawbacks of private properties non accessible in composition of instances across different classes in different files which made me rewrite it using part of and in my opinion its not going away any time soon since many initial libraries still follow this architecture and for a good reason, if in future they deprecate part of then they will surely introduce alternative keyword something like friend of and then we will migrate the code accordingly.

from flutter_janus_client.

for more context look at https://github.com/flutterjanus/flutter_janus_client/releases/tag/2.0.0-beta this release was using exports and imports instead of part of and drawback was in every class properties which are not private are also accessible in ide (intelisense) which end user would not be happy about.

from flutter_janus_client.

with part of we have better control at what we expose as an api.

from flutter_janus_client.

Valid arguments to leave it as is.

from flutter_janus_client.