OOP is better with stamps: Composable object factories. News: https://twitter.com/stampit_org
@koresar awesome! thanks!
by the way was playing around and noticed another IMO unexpected behaviour:
const stampit = require('@stamp/it');
const InstanceOf = require('@stamp/instanceof');
const Request = stampit({})
.compose(InstanceOf);
const ErrorRequest = stampit({})
.compose(Request)
.compose(InstanceOf);
const request = Request();
const errorRequest = ErrorRequest();
console.log('is request instance of Request?', request instanceof Request); \\ => TRUE
console.log('is errorRequest instance of ErrorRequest?', errorRequest instanceof ErrorRequest); \\ => TRUE
console.log('is errorRequest instance of Request?', errorRequest instanceof Request); \\ => FALSE
as far as I know the instanceof operator tests whether the prototype property of a constructor appears anywhere in the prototype chain of an object https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/instanceof
At your link, scroll to bottom, click this link: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol/hasInstance
That is what is being used.
That is what is being used.
We do not recommend you to use
instanceof in JavaScript.
If you need to check an object - duck type it.
Also, please take a look at this picture: https://stampit.js.org/
Stamp's main task is to avoid inheritance chain.
hey @koresar ... I had to dive into older project using stamps and I feel a bit confused right now ... I got so used to regular getters lately, but this seems is not working with stamps right? I can only use more verbose property descriptors
const PaymentRequest = compose(
Storage,
{
init(request) {
this.request = request
},
props: {
get accountId() {
return this.request.x_account_id
},
}
}
)
this kinda fails upon composition because
Object.assign apparently tries to evaluate those getters right away
@FredyC The library looks great, I starred it a long time ago, and now came back to it, because I have some crazy inheritance hierarchy that I want to replace.
I see there is some action on the repo regarding the typescript types and there is
I see there is some action on the repo regarding the typescript types and there is
@types/stampit but trying it in codesandbox I got no type hinting.
@FredyC And of course I want to use it with mobx :)
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/stampit/index.d.ts
there are definitely some types in place, could be working, CodeSandbox sometimes takes time to "heat up" with TS
there are definitely some types in place, could be working, CodeSandbox sometimes takes time to "heat up" with TS
We've released a fresh new d.ts support just few weeks ago
@FredyC the development never stopped.
Second one is a clone which is going to be rewritten in the most modern way with TypeScript
I think I forgot to publish v4.3.1 with the new types file. Oops
I have no idea what is "stamp" library
😂
Imagine =I'm
Do you have any experience with mobx5? It uses proxies to do its magic
Will the usage of proxies be a problem?
Probably proxies are not an issue