1.0 Release Candidate

This release brings:

• Automatic user session fetching from the back-end and proper logging out
• The localized display of date and currency
• Through https://github.com/my-koop/module.event:
  • The possibility for users to register to a current or future event
  • The possibility for administrators to update an event
  • The possibility for administrators to list all events, including past ones
  • The possibility for administrators to begin and end events, while tracking the contents of the register
• Through https://github.com/my-koop/module.inventory:
  • New "section" and "description" fields
  • The possibility for administrators to jump to a detailed view of an item and edit all its fields
• Through https://github.com/my-koop/module.member:
  • The possibility for administrators to mark a user as being a member
  • The possibility for administrators to manage and track member subscriptions and memberships
• Through https://github.com/my-koop/module.transaction:
  • The possibility for administrators to display the closing date of an invoice
  • The possibility for administrators to filter invoices using their opened/closed status
  • The possibility for administrators to attach notes to an invoice
  • The possibility for administrators to configure taxes to be applied on invoices
  • The possibility for administrators to add payments and refund to invoices using the invoice list
  • The possibility for administrators to delete invoices that were never part of any transaction
• Through https://github.com/my-koop/module.user:
  • The possibility for a user to reset his password and have the new one sent to his email
  • The possibility for administrators to assign permissions to users
  • The possibility for administrators to attach notes to a user
  • The possibility for administrators to display which users are also members (Responsibility to be deferred to https://github.com/my-koop/module.member at a later time)
  • Better definition of the login form to allow popular browsers to suggest to remember credentials
• Through a new mailing list management module (https://github.com/my-koop/module.mailing list):
  • The possibility for individuals to register to certain mailing lists when registering for a user account
  • The possibility for administrators to create mailing lists, and decide if they are to be publicly visible
  • The possibility for administrators to edit mailing lists
  • The possibility for administrators to delete mailing lists
  • The possibility for administrators to compose and send emails to mailing list subscribers

For developers:

• Persisted sessions (Through a MySQL store)
• "mykoop" modules discovered through node_modules directly
• Error internationalization strings and utilities
• A rich text (WYSIWYG) editor component
• A set of CSS classes that help prevent the line-wrapping of button groups
• A React mixin that allows to easily display a Bootstrap alert message following an action
• The fixing of a bug where route data fed to front-end actions would also be part of the query string
• Through https://github.com/my-koop/module.user :
  • The possibility to obtain the ID of a user from his email
  • The possibility to define usable user permissions
  • The possibility to validate permissions against a user
  • The possibility to provide tabs to the "my account" page (through meta data)
  • The possibility to provide additional options in the user registration page (through meta data)
  • Back-end route protection using permissions
  • React mixins to faciliate protection of front-end pages
• In the utilities module (https://github.com/my-koop/module.utils):
  • A utility that simplifies the use of MySQL transactions (Moved over from https://github.com/my-koop/module.transaction)
  • New error types: ResourceNotFoundError and AccessDeniedError
• Through a new communication utilities module (https://github.com/my-koop/module.communications):
  • The possibility to send emails
• A template module (https://github.com/my-koop/module-template) updated to be on par with all the API changes

1.0 beta

This release brings:

• A visual feedback (through the form of a spinner) of ongoing network activity in the front-end
• Through https://github.com/my-koop/module.user:
  • The possibility to register for a user account
  • The possibility to login to a user account
  • The possibility to update a user profile and change a user password
• Through https://github.com/my-koop/module.inventory:
  • The possibility to add a new item
  • The possibility to permanently delete an item
  • The possibility to specify a quantity threshold for an item and to list items under their threshold
• Through a new event management module (https://github.com/my-koop/module.event):
  • The possibility to create an event
  • The possibility to list events
  • The possibility to delete an event
• Through a new transaction management module (https://github.com/my-koop/module.transaction):
  • The possibility to create a bill (with basic tax support), and optionally tie it to a user
  • The possibility to mark a bill as paid
  • The possibility to list bills
  • An experimental utility that simplifies the use of MySQL transactions
• A foundation for a member management module (https://github.com/my-koop/module.member).

For developers:

• Validation utilities tied to requests and leveraged both in the front-end and in the back-end
• An error middleware that eases the sending of error messages back to the client (through serialization, see the changes in utilities below)
• A local session store in the front-end
• A global custom alert utility
• A debouncing utility that can be used to process user input with a delay
• Through https://github.com/my-koop/module.user :
  • The possibility to validate a user email
• In the utilities module (https://github.com/my-koop/module.utils):
  • Descriptive error classes with a hierarchy and that can be serialized for eventual transmission over the wire
  • A new utility that simplifies the binding of straightforward requests to a controller
  • A new utility that simplifies the transitioning to other routes in the front-end
  • The renaming of the MetaData utilitiy to MetaDataBuilder, to better convey what it does
• A template module (https://github.com/my-koop/module-template) updated to be on par with all the API changes
• An updated install tool (https://github.com/my-koop/installation) that:
  • Is now checking out the default branch if the directory exists on install
  • Dropped the node-git dependency since it greatly slowed down the install time of the tool

1.0 alpha

This release brings:

• Modularization of the ecosystem where each "role" can be defined by an independent module (see https://github.com/my-koop for a list). The system currently allows a module to expose the following to the core system and thus to the other loaded modules too:
  • New pages
  • New UI components
  • New UI styles
  • New localization strings
  • New frontend routes
  • New backend routes and request handlers (a.k.a controllers)
• A foundation for a user management module (https://github.com/my-koop/module.user) and an inventory management module (https://github.com/my-koop/module.inventory).

For developers:

• An install tool that allows to easily check out and setup the whole project stack (https://github.com/my-koop/installation)
• A logger utility that supports log levels, meta data, multiple transports and that helps trace back the messages' origin. (https://github.com/my-koop/module.logger)
• A utilities module which simplifies common tasks. (https://github.com/my-koop/module.utils)
• A database module which exposes MySQL through https://github.com/felixge/node-mysql. (https://github.com/my-koop/module.database)
• A maintained module template to help get started on a new module and keep up with changes to the core API. (https://github.com/my-koop/module-template)

Prototype

Prototype showing some pages with mock data illustrating the comprehension of the extent of the project and proving its feasibility.