Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Adding support for multiple storage components #920
@dschelchkov : should there be a default value for based_on_storage attribute? I see that is being referenced later as 'key' , but since it's not a required or has a default value will that resulted in the key not to existed? Unless that's the desirable behavior?
That's by design. Basically I need a user's input (or the pack's owner can set it at the pack level) for that attribute. If the value for that attribute is not provided (which is what's gonna happen now for all the existing packs), then the 1st branch of the matching algorithm will not be used. The 3 "branches" are as follows: