companionstudio / islay-shop Goto Github PK
View Code? Open in Web Editor NEWA shop module for the Islay framework
License: MIT License
A shop module for the Islay framework
License: MIT License
The sku_price_logs table is going to be removed, since it's functionality is entirely replaced with the price points update.
Because of the condition scope, adding a code which applies free shipping won't work until there are shipping charges (which there often aren't, at the point a code is entered). For now, I'll just remove the condition scope, so we don't require shipping charges before applying the effect.
Currently these codes are single use only, but it would be good to have them as single, multiple, or unlimited use.
For example, if two promotions apply free shipping, they will combine their discounts leaving the total with a negative amount. Basically, all line-items should be bound to zero at the lower end.
Currently they're fired off inline with any order processing. This is a problem, since an exception when sending an email can hose an otherwise valid transaction.
Currently the effect and condition loaders only consider files in the engine's code base. We need to allow including apps to provide their own and have them loaded.
Looks like a regression from an update to SpookAndPuff::Money, which isn't a dependency of SpookAndPay. Islay Shop needs to check the payment provider and provide the right value (bit icky).
They should be displayed pretty much everywhere in the catalogue. Overview, category, product and stock level indexes.
It would be convenient if the user could optionally add a default SKU when creating a new product. This would save a bit of busy work.
This needs to take into account the countries available for delivery, and restrict the delivery address options as appropriate.
Promotions which have a shipping effect should have a corresponding condition which enforces:
a. Order has shipping service
b. Shipping total is greater than zero
Then the condition_scope for each could be defined as :shipping_service. The end result of this is that discounted shipping can only be offered when orders have shipping charged against them; avoids the nonsensical effect of discounting shipping that is already free.
The user should be able to add multiple assets, much as they can with products.
When updating a SKU, the validation failing (for example a missing value for Freight Class) will cause an invalid price point to be inserted into the form - in turn this breaks validate_boxed_and_bracketed_overlap
or any other method which relies on sorting by volume.
Categories can be nested, but we don't present a UI for managing this to the user.
order and conditions keys need to be converted to the proc syntax
Currently conditions can optionally include a Hash of targets when returning a result via #check. This count is used by effects to decide the results of their application. For example, the Get N Free effect needs to know how many items qualify.
However, with some conditions there is a difference between the number of order items which are considered as qualifying and a count of qualifications. This is a subtle but important difference.
For example, consider the Quantity conditions. If we configure a condition that says buy at least 5 of SKU foo, and an effect which is 10% off each qualifying item.
Without this distinction between qualifying and qualifications, the discount effect would only know about the single qualification, not the count of items that were used to determine the qualification.
Here is a slightly more complicated scenario. A condition is specified that says for every 10 of SKU bar, and an effect that says $2 off each.
Now, imagine the above scenario, but with a Get N Free effect. In that case the promotion described would be 'For every ten of SKU bar get one free'. In this example, the effect needs to know the number of qualifications, not the count of qualifying items.
When viewing details for a promotion, the user needs a way to get to the codes - either single or unique.
The decorator blows up when trying to produce a summary:
undefined method `sku' for #PromotionBonusEffect:0x007fc633cffa20
For example, when listing orders, have aggregate counts for things like total orders, pending, cancelled etc.
The same could be done in may other places e.g. promotions.
Concerns fit the Rails 4 model better, and won't mess with the Autoloader.
They currently show the current month, and have logic for other date ranges, but there's no way to select them in the UI.
Sometimes the generated summary just isn't what's required. Simplest solution might be to just have a field which can override the whole generated summary.
At the moment it's undercooked. Badly styled and showing enough useful information. Some kind of report/overview of sales would be useful.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.