Rainbow OF is a Rainbow Order Fulfilment that is an open source solution to managing order fulfilment from WooCommerce to the customer.

Designed to pull data from Woo, or import from a legacy system it handles the order from placement to fulfilment. Minus the accounting.

Main Web Project is RainboeOf.Web.FrontEnd

The project uses a SQLConnection string set in appsettings.json. Once you have updated the string to point to the correct SQL instance in the appsettings.json. The do an add-migration to build the database using EF Core code first. The best project to do the migrations in, is RainbowOF.Data.SQL. Currently the migrations are stored there, so you will need to delete them so that a new one is created.

There is no sample data, you need to pull data from your Woo site.

Trying to follow -> https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions

• Local class variables: "_" prefix with Pascal case similar to the class name.
  • Exceptions:
    • When using a model. then use the word model as prefix to the Pascal case with the.
    • Reference variables to be used in child components are preceded with Ref.
    • Event reference variable with Event as a suffix
    • Also boolean's are Prefix with Is or Do as Pascal case.
    • Component Parameters PascelCase no "_" with a word prefix Explaining source SourceXXX or ModelXXX etc
• public interface variable camelCase (no I)
• Local function/routine variables: "_" prefix with camel case.
• Parameters for procedures: where appropriate use a word prefix to explain the parameter action (like delete or update or new) or use the prefix "p" but make sure you add a comment about using ///

enums: to be in camel case.

• Tables are named as the plural of the class that is a single record in the table.
• All Lists in each class will also be plural.
• All ID fields are the same name as the Single record suffixed with "Id".
• All models / database classes are store in RainbowOF.Models

A draft design document call RainbowOfDesignAndDocumentation.doc is in the root folder.

• Basics Settings
• Woo Settings integration
• Initial Woo import including:
  • Categories
  • Attributes
  • Attribute Varieties
  • Items (only parent and essentially data)
• Tools, including:
  • Basic modal support
  • Colour picking tool
  • Toast messages (may migrate to blazorise solution)
• Items:
  • Category Lookup Component, including filter, sort and paging support. Also CRUD with Woo integration.
  • Attributes Lookup Component, including filter, sort and paging support. Also CRUD with Woo integration.
  • Attributes Varieties Lookup Component, used in Attributes Grid, and also in Attribute Varieties. Filter, sort and paging done. CRUD done with Woo Support
  • Items Grid View component. With filter, sort and paging support. Editing moved to separate component
  • All done using an interface that adds a view then has similar CRUD / Filter / Sort / Paging calls

• Update of design / tech document
• Complete the Items edit:
  • Integrate categories, specifically predicable / trackable categories
  • Integrate attributes, specifically variation attributes so that Item variations (or children) can be created and displayed.
  • Add a Woo Sync to pull the Item Variations (to be done via an interface that allows Woo Import to use it
  • CRUD support to and from Database and also with Woo integration
  • Complete Woo Import of Items to include variables
  • Display only parents or parents and child with a sub-grid in items view

• Each section will first be added to the design then do. OPnce done the design doc is to be reviewed, and updated with a status.
• Additional item types - GroupBy / virtual (is this a type or a separate setting?) / collections
• Contacts all of it, including:
  • Data
  • Woo
  • POPIA
  • Accounts?
• Orders all of it, including:
  • Data
  • Woo
  • Delivery sheet management
  • Predications ?
• Third Party manager / Repairs (was called repairs move to third party)
• Reminder emails and notifications including
  • Prediction (do we store in a table or calculate?
  • Mobile?
• CSV Import (of the old data, but also support of the new stuff)
• Fix menu to be more like blazorise
• Security:
  • Google / ms single sign on
• Auto Creation of sample data and table
• Move to Cloud database.

• Open source the project?
• Fix the import to fire tasks so that it imports n products at a time - so more async
• Mobile app to allow orders and tracking
• Sage / Accounting integration
• Item Templates > creation of items based on templates
• SAS version and model (free for x and then price brackets).