1.0.0-rc.1 released; stable API is here

I'm thrilled to announce the release of the 1.0.0-rc.1 version.

So what does this mean for you? It's a pledge that there will be no further BC breaking API changes. The API you build on today is the API you can rely on.

Why am I confident enough to commit to that? Because Wraplet is (and has been for quite some time already) 100% covered with tests, including branch coverage. It was tempting to push out a 1.0.0 release right away. For long-lived projects a certain caution is required, though, and it's best to exercise it from the start, so we'll move slowly and strictly follow the SemVer rules.

One thing worth clarifying: the stability pledge doesn't mean the base classes you extend are frozen solid. Within minor versions Wraplet may still add new methods and properties to them as its capabilities grow — in particular lifecycle methods whose names start with on. To stay on the safe side, treat the on prefix as reserved and avoid using it for your own methods on classes deriving from Wraplet, so a future addition can't clash with them. We'll be careful about the name clashes.

It doesn't mean that the development stops here, but it needs to be redirected temporarily. So what are the current goals? Let's see.

• Writing benchmarks for the js-framework-benchmark.
• Expanding the ecosystem by developing libraries and tools powered by Wraplet, being living examples of what Wraplet can do and how it does it.
• Writing more recipes, examples and blog posts showing Wraplet from different angles.

I think the codebase is solid; now it needs to be explained.

In the meantime, if you find any issues, please report them in the issue tracker.

To start developing with Wraplet right now, see: quick start.

You can also participate in the discussion about the Wraplet's future here.

If you are new to Wraplet, you can catch up by reading the introduction.

Happy coding everyone!