[pull] develop from medusajs:develop #636
Open
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 pull request updates the API reference documentation for both the admin and store APIs to include a new method for passing array filters: comma-separated values. It introduces 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
|
FIXES FRMW-2915 **What** Backport metadata management. all the metadata get preserved unless a specific empty string is provided for the key which in turn would remove that key from the metadata
Fixes: FRMW-2913 Related Github issue - #11330
…able information as well (#11489) * feat(framework): Improve production structured logging with more valuable information as well * feat(framework): Improve production structured logging with more valuable information as well * feat(framework): Improve production structured logging with more valuable information as well * feat(framework): Improve production structured logging with more valuable information as well * fix typo * update trust proxy * Create new-ligers-heal.md * revert trust proxy
…#11434) * feat: create product flow changes * feat: allow unsetting SP on product update * feat: update prepare line item helper * test: add testcase * wip: fix tests * fix: update module tests * fix: cart module test
…#11467) * feat(js-sdk): implement custom storage config to support react native * chore: add changeset * feat(js-sdk): implement custom storage config to support react native * chore: add changeset * test: ✅ add unit tests for custom storage
…#11466) **What** - Fixes an issue where we would parse a string like `"52 tests"` into `52` in the Metadata form - If a row is deleted we now send off key with an empty string as its value to signify that it should be deleted. This is needed to introduce the API we had for updating metadata in V1. Adrien is implementing the BE support for this. RESOLVES SUP-895
**What** - Add index engine feature flag - apply it to the `store/products` end point as well as `admin/products` - Query builder various fixes - search capabilities on full data of every entities. The `q` search will be applied to all involved joined table for selection/where clauses Co-authored-by: Carlos R. L. Rodrigues <[email protected]>
* docs: update products user guide * fix broken link
* docs: update inventory user guide * fix build error * fix build
…1511) The `storefrontUrl` is defined in the `packages/core/types/src/common/config-module.ts` file, but for many purposes, including the documentation, we use the types defined in `packages/core/framework/src/config/types.ts`. This PR adds the `storefrontUrl` to the framework type
Fixes: FRMW-2896 Closes: #11502
…shipping options (#11493) **What** - add `insufficient_inventory` flag when listing shipping options for a cart - add `enabled_in_store` flag when creating/editing pickup options
* update promotion pages * finish update * fix build error
**What** - Add index engine sync log information - Ad `setTimeout(0)` to give breath to the event loop and ensuring not blocking the event loop and allow for other tasks queue execution to happen while syncing here is an example: **LOG_LEVEL=info**  **LOG_LEVEL=debug** 
feat: add Quote Management guide
…in,admin-bundler): Fix broken plugin dependencies in development server (#11720) **What** - Reworks how admin extensions are loaded from plugins. - Reworks how extensions are managed internally in the dashboard project. **Why** - Previously we loaded extensions from plugins the same way we do for extension found in a users application. This being scanning the source code for possible extensions in `.medusa/server/src/admin`, and including any extensions that were discovered in the final virtual modules. - This was causing issues with how Vite optimizes dependencies, and would lead to CJS/ESM issues. Not sure of the exact cause of this, but the issue was pinpointed to Vite not being able to register correctly which dependencies to optimize when they were loaded through the virtual module from a plugin in `node_modules`. **What changed** - To circumvent the above issue we have changed to a different strategy for loading extensions from plugins. The changes are the following: - We now build plugins slightly different, if a plugin has admin extensions we now build those to `.medusa/server/src/admin/index.mjs` and `.medusa/server/src/admin/index.js` for a ESM and CJS build. - When determining how to load extensions from a source we follow these rules: - If the source has a `medusa-plugin-options.json` or is the root application we determine that it is a `local` extension source, and load extensions as previously through a virtual module. - If it has neither of the above, but has a `./admin` export in its package.json then we determine that it is a `package` extension, and we update the entry point for the dashboard to import the package and pass its extensions a long to the dashboard manager. **Changes required by plugin authors** - The change has no breaking changes, but requires plugin authors to update the `package.json` of their plugins to also include a `./admin` export. It should look like this: ```json { "name": "@medusajs/plugin", "version": "0.0.1", "description": "A starter for Medusa plugins.", "author": "Medusa (https://medusajs.com)", "license": "MIT", "files": [ ".medusa/server" ], "exports": { "./package.json": "./package.json", "./workflows": "./.medusa/server/src/workflows/index.js", "./.medusa/server/src/modules/*": "./.medusa/server/src/modules/*/index.js", "./modules/*": "./.medusa/server/src/modules/*/index.js", "./providers/*": "./.medusa/server/src/providers/*/index.js", "./*": "./.medusa/server/src/*.js", "./admin": { "import": "./.medusa/server/src/admin/index.mjs", "require": "./.medusa/server/src/admin/index.js", "default": "./.medusa/server/src/admin/index.js" } }, } ```
docs: update sidebars and navigation bar
* docs: add missing details related to links and migrations * reorder content * small changes * last changes * improve examples * fix lint error
* docs: improvement to sidebar * fix sidebar
Fixes: FRMW-2930 This PR updates the MikroORM config to use the module name as the snapshot name when generating migration files. Otherwise, MikroORM defaults to the database name and every time you update the database name, it will create a new snapshot. Also, we migrate existing snapshot files to be same the new file name to avoid breaking changes.
* Polish translations improvements * Improve Polish pluralization rules --------- Co-authored-by: Stevche Radevski <[email protected]>
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
Clarify documentation for array filters in the Admin and Store API references. Provide examples for passing array values as comma-separated strings or as separate query parameters. Include a note about the
-gcurl parameter.Documentation:
-gparameter incurlcommands