Roadmap
This section talks about the upcoming releases, and the requirements for each and also describes the general gist of each release.
Each release will define the features that are planned for the release, these features may be added to, removed, or moved depending on the progress for that release.
Each release will be named after a random fruit that would be good as/in a fizzy drink (IMO), like raspberry. 👌
V1.0.0
- Cherry
Overview
This release focuses on stability, this is ensuring that there are no major bugs or issues with the framework, and ensures all packages are doing what they should.
Features
Status | Description |
---|---|
✅ | @sodacore/discord package. |
❌ | Document the OAuth2 authetication for the @sodacore/discord package. |
❌ | Implement more helpers for @sodacore/discord package when crafting prompts and responses. |
❌ | Refactor the @sodacore/core CLI scripts handling service to be more robust and less error-prone. |
❌ | Create the @sodacore/i18n package and then ensure all packages can utilise this feature for errors, messages, etc. |
❌ | Remove @sodacore/ws 's reliance on @sodacore/http so that a WebSocket can be setup without needing to create an HTTP server. |
❌ | Look into offering some kind of TCP / UDP offering as well, so that we can offer a more generic socket server. |
❌ | Implement authentication guards that can be used "generically" across all packages. |
❌ | Implement a generic router system for input and output, this should make it easier to work with authentication guards and i18n. |
❌ | Finalise the @sodacore/di package, including implementing auto-DI for @Injectable classes (Drop the feature if not able to implement cleanly). |
V1.1.0
- Lime
Overview
This release will focus on additional packages that revolve around user interfaces, the framework is primarily a service handler, where various packages offer a service that is exposed, and the framework offers a kind of "opinion", i.e. all packages are built around the same idea, and the same way of doing things, this will allow for a more seamless experience when using the framework. In this release we want to focus on creating almost a way of creating a visual view of building web pages. For example a user could make a simple blog or an admin dashboard.
Features
Status | Description |
---|---|
❌ | Implement the @sodacore/vite package offering the Vite dev server with HMR, and production static builds and even offer a way to deploy a SSR version as well. |
❌ | Implement the @sodacore/ui package, this will be a functional user interface based around the PageVue idea, where users can create, and implement their own pages using a set of pre-defined components, with the ability to integrate "other" packages and their components. |