Frotty

So according to @peq this is fixed, but an issue can still occur if the package is a dependency and not yet imported into the user's project.

yes, i know that you can workround this with init funcstions and such and i was about to add it to the ticket - but it shouldn't really matter to...

The biggest problem with this is inheritance. You have to call super first so you cannot call your custom init function. Either do this or https://github.com/peq/WurstScript/issues/158 to fix it please.

I think the easier and more comfortable way would be to offer a quickfix for private variables, to generate a setter and a getter function automatically.

Yea could be added, but such injections are always a bit ugly imo. If the only reason is to play a song in the lobby i don't think it's a...

where is option d) ? 🔸 I think the e) solution sounds good. Probably that file should even be generated by the setup/DM when updating the dependency? Wurst should just...

What do you mean? There is no way for multiple languages except generating every object it multiple variations or so. Doesn't seem very feasible.

there currently is nothing like that, but it could be done, perhaps a PR? Also still needed for long entries over 512 characters iirc.

> 1: Is it necessary to alert for grammatical inconsistencies? I'm not sure what you mean by "grammatical inconsistencies". In general warnings try to incentivise following [Coding Conventions](https://wurstlang.org/manual.html#coding-conventions). > I...

> mean `aaa()` and `aaa ()` and `aaa( )` Yea, I think those should be warnings as well. Just like [TSlint](https://palantir.github.io/tslint/). > i think it base on `common.j` and `blz.j`...