[pull] develop from medusajs:develop #10
Open
+1,198,947
−701,641
Conversation
This file contains 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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Reviewer's Guide by SourceryThis PR updates the Medusa project to version 2.1.3, updating core modules and dependencies to the latest versions. No diagrams generated as the changes look simple and do not need a visual representation. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
* feat(core, medusa): Enable migration scripts * spacing * rm unnecessary import * Allow to skip script migration * fix missing options * add options * add tests and small changes * update * add checks * add lock mechanism to be extra safe * Create six-bears-vanish.md * update queries * fix tests --------- Co-authored-by: Oli Juhl <[email protected]>
…sponse (#10970) Co-authored-by: Oli Juhl <[email protected]>
…10961) Co-authored-by: Oli Juhl <[email protected]>
* feat(core-flows): validate hook * rm only
**What** Fix index engine query builder to include column type casting on order by Co-authored-by: Carlos R. L. Rodrigues <[email protected]>
* fix: Correctly parse Stripe error, remove unused method * fix: Isolate the payment provider error check function * fix: Allow passing few extra parameters to Stripe --------- Co-authored-by: Oli Juhl <[email protected]>
…10962) * chore(core-flows,types): improve TSDocs of cart workflows and steps * fix build errors * fix build error * fix errors
…kflows / steps (#10993) * improve customer tsdocs * finished improving tsdocs * fix build error
…rt query (#10990) **What** - Exclude definition file from the glob search string - Properly generate the insert query string
…11000) * chore(core-flows,types): improve tsdocs of pricing-related workflows * fix build error
* chore(js-sdk): update TSDocs of auth callback * generate doc
…ons (#10950) what: - adds a status column to promotion table - introduce active promotion query - scope revert, register and compute actions to active promotions - admin to create and update promotion with statuses RESOLVES CMRC-845 RESOLVES CMRC-846 RESOLVES CMRC-847 RESOLVES CMRC-848 RESOLVES CMRC-849 RESOLVES CMRC-850
CLOSES CMRC-760
* chore: fix manage customer groups of customer OAS * fix validation error
…min/refund-reasons/:id (#11012)
…1336) **Why** - if pending difference is lass then the rounding threshold for currency the page would show for example "Refund -0.00$" **What** - example: hide the refund button if the pending difference in USD is -0.004 - example: show refund button if pending difference on USD is -0.007 --- CLOSES SUP-811 CLOSES #11331
…ages and align Vite version (#11361)
This PR adds a couple new statuses to the payment collection and payment webhook results. The payment collection will now be marked as "completed" once the captured amount is the full amount of the payment collection. There are several things left to improve the payment setup, so non-happy-path cases are handled correctly. 1. Currently the payment session and payment models serve a very similar purpose. Part of the information is found on one, and the other part on the other model, without any clear reason for doing so. We can simplify the payment module and the data models simply by merging the two. 2. We need to handle failures more gracefully, such as setting the payment session status to failed when such a webhook comes in. 3. We should convert the payment collection status and the different amounts to calculated fields from the payment session, captures, and refunds, as they can easily be a source of inconsistencies.
* fix: update variant flow for prices * fix: import add test * fix: test name
* chore(types,framework): pick ssl types from tls lib * chore: call from node:tls directly
* docs: update default NODE_ENV * fix * fix
* docs: document payment changes + account holder * added version
Co-authored-by: olivermrbl <[email protected]>
* chore(docs): Generated DML JSON files (automated) * fixes --------- Co-authored-by: olivermrbl <[email protected]> Co-authored-by: Shahed Nasser <[email protected]>
Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action Co-authored-by: Oli Juhl <[email protected]>
Generated the following references: - `api_key` - `auth` - `cart` - `core_flows` - `currency` - `customer` - `fulfillment` - `inventory_next` - `js_sdk` - `medusa` - `medusa_config` - `modules` - `modules_sdk` - `notification` - `order` - `payment` - `payment_models` - `payment_provider` - `pricing` - `product` - `promotion` - `region` - `sales_channel` - `stock_location_next` - `store` - `tax` - `types` - `user` - `utils` Co-authored-by: Oli Juhl <[email protected]> Co-authored-by: Shahed Nasser <[email protected]>
* added hook for createApiKeysWorkflow * fix types * fixed typings for createApiKeysWorkflow
* chore(docs): Generated API Reference (automated) * fixes --------- Co-authored-by: olivermrbl <[email protected]> Co-authored-by: Shahed Nasser <[email protected]>
Folder was previously named calender (sic)
CLOSES CMRC-917
**What** Fix linkable generation when there is no dml models and models are provided as virtual to the joiner config and therefore the linkable are inferred
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )
Summary by Sourcery
Update dependencies to 2.1.3 and add support for custom line items.
New Features:
Tests:
useQueryGraphStepinstead ofuseQueryStep.getItemTaxLinesStep.