Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] develop from medusajs:develop #19

Open
wants to merge 199 commits into
base: develop
Choose a base branch
from
Open

Conversation

pull[bot]
Copy link

@pull pull bot commented Jan 16, 2025

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 : )

carlos-r-l-rodrigues and others added 2 commits January 15, 2025 18:49
* 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]>
@pull pull bot added the ⤵️ pull label Jan 16, 2025
thetutlage and others added 27 commits January 16, 2025 11:06
* 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
* chore: fix manage customer groups of customer OAS

* fix validation error
RESOLVES FRMW-2875

**What**
Allow to generate migration for plugins. Migration generation defer from project migration generation and therefore we choose to separate responsibility entirely.

The flow is fairly simple, the user run `npx medusa plugin:db:generate` and the script will scan for all available modules in the plugins, gather their models information and generate the appropriate migrations and snapshot (for later generation)

Co-authored-by: Harminder Virk <[email protected]>
shahednasser and others added 30 commits February 3, 2025 14:34
* docs: document variant inventory conceptual guide

* add notes

* fix vale error

* fix vale error
* docs: document Query Context

* add vale exception
- Add missing translations for inventory stock management
- Fix customer groups list structure
- Add missing order fulfillment error messages
- Update promotion status structure
- Add missing shipping options translations
- Fix various translation inconsistencies

Co-authored-by: epaprat <[email protected]>
**What**
- validate that there is a shipping method if any of the line items have requires_shipping=true
- validate that products shipping profile is supported by a shipping method on the cart
- update tests

---

CLOSES CMRC-683
* added route to book

* added to resources

* added route to ui

* added to user guide
**What**
- Adds missing Metadata form for collections
- Fixes type of metadata in update payload
- Fixes an issue where deleting the last row of a metadata form would prevent adding new ones.

Resolves SUP-784
* initial

* improvements

* finished implementation

* transform links to index.html.md links

* fix for resources
**What**
- prevent unsetting shipping profile on product update
* docs: fix appending index.html.md to api reference links

* make hash in api reference lower case
Closes: FRMW-2892, FRMW-2893

**What**
Wired up the building block that we merged previously in order to manage data synchronization. The flow is as follow
- On application start
  - Build schema object representation from configuration
  - Check configuration changes
    - if new entities configured
      - Data synchronizer initialize orchestrator and start sync
        - for each entity
          - acquire lock
          - mark existing data as staled
          - sync all data by batch
          - marked them not staled anymore
          - acknowledge each processed batch and renew lock
          - update metadata with last synced cursor for entity X
          - release lock
      - remove all remaining staled data
    - if any entities removed from last configuration
      - remove the index data and relations

Co-authored-by: Carlos R. L. Rodrigues <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.