After the initial work with the JS SDK, we encountered some substantial issues which made development very hard. For example:
• generated code (stampit) hard to use – very un-javascript
• documentation is still lacking (e.g. the entry point documentation for all SDK features: https://github.com/aeternity/aepp-sdk-js/blob/develop/docs/api/ae/universal.md is not very thorough and there’s no minimal working example in the README/docs that just works)
• our first running test case suddenly stopped working – the errors thrown were not really helpful
I appreciate that this is all alpha at the moment – but is there some official roadmap or estimate when the JS SDK will be production-ready?
1 Like
Hey thanks for letting us know. Maybe @emin.chain or @pegah.chain can help here.
2 Likes
Hey Erasmus:) Naz from the JS-SDK team is already on it! 
We’ll let you know whenever it’s going to be ready 
Best,
Pegah
2 Likes
Hey @erasmus,
Nice to e-meet you and thank you for your feedback.
generated code (stampit) hard to use – very un-javascript
Stamps are a different software development paradigm and it gives us more flexibility than usual Class syntax inheritance.
Stampit library enables us to follow concept of composition over inheritance .
This blog post more deeply describes about how it works.
You can also have a look at the principles our SDK follows here.
documentation is still lacking (e.g. the entry point documentation for all SDK features: https://github.com/aeternity/aepp-sdk-js/blob/develop/docs/api/ae/universal.md 3 is not very thorough and there’s no minimal working example in the README/docs that just works)
The API documentation is not so simple because of the use of composition.
We are currently working on improving the documentation and we plan to prepare testable examples for each sdk parts.
Also you can find some code example here.
1 Like