is there a way to prepend the `com.whatever.whatever` for import statements one platform, but not an...

# multiplatform

[Jess Brent]

is there a way to prepend the com.whatever.whatever for import statements one platform, but not another? i can’t really come up with the exact phrase to google here so i’m a little SoL

[emmano]

You mean for one platform to have one package name and another platform another package name?

[Jess Brent]

the default configuration appears to not contain the a package structure similar to how people normally set up libraries, where the package directive is something more like the above. i’m assuming there’s a way to do this without changing the entire project’s structure

[Jess Brent]

i’m not so familiar with gradle..

[Jess Brent]

in javascript we never really imported things in this style of “com.company.library”

[emmano]

I am not sure if I am following, but I would create the package and then move the classes into it? Android Studio can help.

[Jess Brent]

i assume i would have to do this for all compilations. i’m trying to avoid this for js

[Jess Brent]

i gave up and did it that way anyway, too frivolous to worry about imo

[galex]

I’d like that too. In JS we don’t need a package as everything is inside a module/namespace, but it is useful on Android and iOS.