Access non-decorated function

First of all, thanks for this sweet library!

I start using it and I don’t get one thing. I have the following:

 makeAwsomeString(): string {
}
  @Action({ rawError: true })
  async doSomething(data: { email: string }) {
    this.makeAwsomeString() /// this causes an error 
  }

When I call makeAwsomeString from an Action I’m getting:

error in v-on handler (promise/async): "typeerror: makeAwsomeString is not a function"

Whats the issue here and how can I solve it?

[nsorin]

This is should be considered a bug, for two main reasons:

• It makes it impossible to outsource instance logic in reusable methods unless one misuses the “Action” paradigm. Sometimes the called method needs access to this, for instance to call getters, without being an action. So the solution proposed by @fen89 has its limits.
• It produces an unexpected behaviour that is very hard to debug. By TypeScript/JavaScript standards, @eikebartels 's makeAwsomeString method should be callable from doSomething. It is not obvious at all when looking at the code that such a thing is not possible.

Stripping code from the original class seems like a terrible idea that can only cause headaches to the users. At the very least, private methods should be kept, since their very purpose is to be called by other methods.

[msmsimondean]

I’m not sure the work around works when you want to call non-decorated private functions from a mutation rather than from an action. I’ve got some helper functions that need to be able to both get and set state and I can’t call them from my mutation