Closed eladchen closed 7 years ago
Thanks @eladchen !
You won't believe, but I'm working on that exactly right now. :)
Also, your first link is for stampit v2. Whereas only stampit v3 (coming soon) is compatible with stamp-specification.
Yes, stampit v2 does not follow the specs.
Do you have any other questions or suggestions?
Oh cool.
Do you have any other questions or suggestions?
- Perhaps the fact version 2 doesn't follow the specs could be pointed out somewhere ?
- I'm looking for a way to handle the collision of two properties in two different stamps with the same name ( ie, stampOne & stampTwo both have the same named property ) But I feel like this needs be in a different discussion. What do you think?
Cheers! :)
Btw, the final stampt v3 PR is coming today. You might wanna join and review it. There are only docs change mainly. My English requires double checks usually as you might noticed. :)
v3 published. Docs in sync (except for the "advanced_exampled.md").
I think the docs for stamps init methods is out of date.
This section suggest that init methods are called with one argument, which is, an object containing 3 properties "instance", "stamp" & "args".
While this section ( @stamp-specification repo ) suggest that init methods are called with two arguments, the first is "options"and the second is the same as the one described in the previous paragraph.
To make things even more clear, the first section describes this signature:
While the second describes this signature:
Is this intentional? And if so, does it mean stampit version 2.x doesn't follow the specs ?