Closed lornally closed 5 years ago
i have push the pr, and, because the eslint error, so i do a prettier format, sorry.
No worries mate. All good. I'll take a look later.
sorry there is a format error, too.
sorry, mate, there is error still, and i can not deal it. help :)
I will take a look today or tomorrow. Very busy at work currently. Sorry about that
you are welcome. and ask a digression from this issue, how can you react so in time? you can receive some github message? or maybe we can contact each other with some IM tools.
@lornally I do receive emails for each of the issue, PR or comment. :) You can reach me on twitter https://twitter.com/kore_sar
thank you, i will set github so i can receive the mail too. btw, the pr can pass npm test, but can not pass CI. my email: machangkun@me.com, we can connect by email too.
hi, mate, can we continue?
Yes we can. But after this one merged. https://github.com/stampit-org/stamp-specification/pull/128
The specification is a crucial part of the project. Every module which implements the stamp specification must fully comply.
Thus I believe it would be a good idea to wait for the next version of the specification.
Sorry I didn't mention it earlier
On Thu., 27 Jun. 2019, 18:11 茂弘, notifications@github.com wrote:
hi, mate, can we continue?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/stampit-org/stampit/pull/345?email_source=notifications&email_token=AAMMELYE2JTXURD773ANGB3P4RYZTA5CNFSM4HW2G3WKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYWKEOQ#issuecomment-506241594, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMMEL3RUBG3MKVL245R3ELP4RYZTANCNFSM4HW2G3WA .
ok, no problem, you are welcome, let us do it, we can build the specification now:)
Implemented with #346
maybe deep, static, property and method clone need fix.