Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Catalog defines a `plansAllowedInBundle` but does not seem to be used
See original GitHub issueI am also not quite sure about the semantics. I believe that would define how many subscription of a particular Plan could exist within the same bundle.
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Product Subscription Issue - Google Groups
Hi Nethaji,. Your catalog looks correct -- it seems though that the entry in the cache and/or in the database is corrupted.
Read more >undefined – Kill Bill
The Catalog is at the heart of the Kill Bill subscription and billing systems. It provides complete current information on products available, subscription ......
Read more >Kill Bill - GitHub Pages
Another common use case is to configure both a production tenant and a test ... Each deployment has its own separate configuration, catalog,...
Read more >The difference between a Data Catalogue and a Data Glossary
A Data Glossary defines the terminology which organisations use when discussing their processes and their data. It is purpose is to define the ......
Read more >Data Dictionary vs Data Catalog vs Business Glossary
What is the difference between a business glossary, a data catalog, and a data dictionary? Learn how to use each one for your...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@javier-gomez-hs I would change the default limit to be unlimited (that would keep it consistent with what we had before, since this was not implemented), and so as a side effect tests should still pass in their current form.
@javier-gomez-hs yes you are correct that the bulk creation should also enforce the
plansAllowedInBundle, but i would not make the check at the JAXRS level. I think all those checks should belong to the low level subscription module (where catalog has already been injected). In that specific use case, this would happen here.