You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Q3: In my understanding, Puppet should be an interface definition, different protocols to implement different classes, but some methods of Puppet have logic, and they cannot have logic in Go's interface definition. I don't know what to do.
Sorry, maybe my understanding of wechaty and wechat-puppet is too simple, and I may need to read and understand them as a whole.
If I'm understanding correctly, our problem is the Go Lang does not permit an abstract class to have any implementation in it?
You know there is a tool to "Convert TypeScript types to GO" right? -- https://app.quicktype.io/#l=Go
Meaning that we should make TypeScript type definitions as individual files, separate their implementations from them. So whenever the types get changed, the Go/Java/Python type definition files can be changed semi-automatically as well. Maybe it is already happening, but I'm just shooting into the dark.
@suntong Thank you very much for letting us know the "Convert TypeScript types to GO" project!
I believe that's definitely we should use because the wechaty-puppet will be upgraded frequently and we have to build an automation process to sync other languages like Go from the TypeScript without needing any human helps.
Questions from WIP: add user/message.go #4
Q3
If I'm understanding correctly, our problem is the Go Lang does not permit an abstract class to have any implementation in it?
Please feel free to correct me if I'm wrong.
To be updated... I'm going to study Go now...
Updated Links
The text was updated successfully, but these errors were encountered: