Introduce OrderModel and supply/demand protocols for backend - #13
Merged
Conversation
Introduce base OrderModel and specialized OrderSupplyModel and OrderDemandModel protocols for the backend domain. OrderModel is Codable & Identifiable and defines a generic quantity and createdDate. OrderSupplyModel and OrderDemandModel extend OrderModel and Articlable, adding domain-specific quantity types (Supply/Demand), timestamps and an optional countryCode/shippingDate for demands. Also add a Supply typealias (Float) on OrderSupplyModel. These types provide a structured contract for supply/demand orders in the FunicoERP backend.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces new protocols and type definitions to support order demand and supply modeling in the backend of the
funico-coreproject. The main focus is on defining clear interfaces for order-related models, including demand and supply specifics, and establishing type aliases for better code clarity and maintainability.Order modeling protocols:
OrderModelprotocol, which requires conforming types to beCodable,Identifiable, and to have a mutablequantityproperty (Float) and a read-onlycreatedDateproperty.OrderDemandModelprotocol, extendingOrderModelandArticlable, introducing properties forquantity(of typeDemand),remainingdemand,shippingDate,createdDate, and an optionalcountryCode.OrderSupplyModelprotocol, also extendingOrderModelandArticlable, with aquantityproperty (of typeSupply) and a read-onlycreatedDate.Type definition:
SupplyasFloatwithin an extension ofOrderSupplyModelfor clearer semantic usage of supply quantities.