Future Roadmap

[sewakghali]

Hi maintainers. You guys are doing a great job keeping this project alive, but I think it is time to move forward and start building a development plan, and not rely on simc, because we dont know how long it is going to take because we have not heard much from the author. If you guys could draft a development plan regarding what features are required, and what priorities need to be handled first so that this project can move into a more promising stage, because right now, this project lives in the shadow of its parent.

[arnab]

Additionally, even though this community fork was created with the idea to keep the (at that time, and still today) v3 version up-to-date with dependencies (as noted here), the last release was 3.1.8, almost a year ago now.

Would it be possible to create a new version with updated dependencies? I am sure many existing users are stuck - like I am - with older versions of other packages like build_runner, riverpod_generator , freezed etc. because the community fork version of isar has not been updated for so long.

And if you need community help, I am happy to take some time and do it too. But would need some guidance on what to test etc.

[vicenterusso]

This is a kickstart to our package on pubdev:

https://github.com/isar-community/isar-community

For now I updated source_gen with help from @callumw-k's PR #122

This project is a direct continuation from isar-community/isar, so it will be version 3.2.0. Nexts steps:

• Update more packages
• Update for 16KB page size
• Finally publish minimal acceptable version

I really want PRs for that new repo. All tests are passing so we must keep 100% of tests green