Vasyl Boroviak

Thanks for the info @Sigfried Just a quick note. The approach is memory heavy. **This attaches methods not to the prototype, but to the instance itself.** ```js export class ConceptSet...

@FredyC you are right. But Sigfried do not need method binding and private props.

Sigfried, you can surely do the same using stamps. ```js import {init} from `stampit`; export const ConceptSet = init(function () { // ... constructor code here ... // this.cids =...

Correct. But I still would recommend using `methods()` if you are creating a lot of these objects. Always glad to help!

Polluting `Object` prototype? :) Maybe next time.

Exactly. Stamps are object. Arrays are objects. Going further, classes in Java/C# are also objects of a special kind. Why stamps can't be one of them? :)

Having `stampit`, `react-stampit`, `supermixer` and, hopfuly, `babel-stampit` someday we should consider moving all that to an organization: `github.com/stampit`.

This is an amazing idea! I need some time to work this all out. Thank you. PS: feel free to drop more ideas.

I get exactly the same problem as the screenshot. This literally means the GraphQL API users can't pass `$input` variable like at all! I believe this line passes wrong `variables`....

I believe syntax highlight detection is different per framework. Example. 1. Gatsby - `graphql( ` 2. Apollo - `gql( ` 3. My project - `dispatch("graphql/query", ` 4. VSCode defaults -...