Path to version 1.0

[ashokgelal]

We have already used Alpas in a few production apps and as we were writing those apps, Alpas went through some significant improvements and stability. There is even a full tutorial app written in Alpas that goes to show you that you can already write a complete app in Alpas. However, we still have few things to address, resolve, and add before we can tag it as version 1.0.

There is no plan to make any significant API changes. As I said, we have already gone through refactoring and design changes while we were working on real apps. But still, consider the current state of Alpas to be unstable and having bugs—both major and minor. Feel free to experiment by writing apps and let us know if you run into any issues.

Here are some non-exhaustive list of things, in no particular order, that I want to get done before 1.0 release.

• Add support for Web sockets.
• Improve database support for vendors other than MySQL.
• Improve Windows support with GitBash and WSL.
• Add Windows support without GitBash or WSL.
• Add more tests. My goal is to have at least a 90% test coverage.
• Improve testing both in terms of features and performance.
• Handle multi-part form input.
• Add KDoc comments and make it available for online browsing.
• Add more validation rules.
• Finish documenting the core as well as secondary packages like Pulsar.
• Add more examples to Ozone documentation.
• Add resource routes.
• Allow middleware sorting.
• Allow multiple static assets location. Allow handling multiple static assets locations #8
• Find a way to reload static assets without re-compiling during development.
• Support localization.
• Add database notifications.
• Significantly improve the performance of the queue worker and preferably rewrite it using co-routines.
• Add Code of Conduct.
• Add asynchronous support.
• Improve installation and setup process.
• MySQL 8.0 connection issue. Error connecting with a MySQL 8.0 server instance on Windows #7
• Make routing more strongly typed
• Allow to seed a database easily
• Allow to create an entity instances using a factory
• Allow to hook into a call lifecycle
• Allow template hot reloading
• Enable regex in the routing
• Add more convention based APIs to Ozone
• Add server side events
• Add support for eager loading

If you’d like to take an initiative on implementing any of the big features listed above, please get in touch by reaching out to us on our official Slack. We will offer any help you need to get it started and get it done.

Thank you!