Reactabular 1.0.0-rc8 out - Feedback welcome!

Functionally speaking this is a small release. If I did everything right, nothing should have changed (for good or bad). The biggest change was that I ported the project to use Lerna. It’s a monorepo consisting of smaller packages now.

The old reactabular package should work still. In addition, you can find the other functionality under npm. So in theory you could pick up smaller packages to use in other projects without having to pull whole Reactabular.

The change enables me to develop more little packages and not all of those will go to the core. There’s still something resolution related I want to investigate with @skosch, but apart from that we should be ok for a final release.

I still have to figure out how to manage the versions. One option would be to do Babel style (all package versions are synchronized) or handle them individually. I’m currently opting for the latter though former has its benefits too.

You can install the release candidate through npm i reactabular@rc8.

[bebraw]

If you handle versions individually, would you still follow SemVer conventions in the sense that anyone could rely on packages of identical major versions being compatible?

If I do a breaking change to something like reactabular-sort and reactabular is at 1.0, then I would have to bump reactabular to 2.0 to comply with SemVer while reactabular-sort could go from 0.1 to 0.2 (assuming current version).

I guess the worst case is that we would end up bumping the version of reactabular a lot given it’s aggregate of those other packages.

I don’t know if there’s a good solution to this. If the API breaks, then the versions should definitely live according to SemVer.

[bebraw]

Final 1.0 is available now. A couple of notes:

• I fixed a resolve related issue. Now it’s possible to chain the variants in a reasonable way without losing any data in between. So you can resolve nested data before running it through resolve
• I improved the documentation a notch. There’s a dedicated CRUD example. You can also drag and drop rows now.
• The drag and drop work revealed a small issue in resolving nested props at column definition. props nested in columns should work now.

I ended up using synced versioning mode. This is the way Babel uses. So all of the current packages will be 1.0, etc. It might lead to version inflation if we do a lot of breaking changes, but the API feels solid now so I hope to avoid that.

I still intend to release more specialized packages around the core to make the functionality easier to consume. But that’s something for the next days.

Thanks for the reports during development. I hope you enjoy the release.