Feature/cmg 705

[aishwarya-cstk]

No description provided.

[Copilot]

Pull request overview

This PR updates the WordPress migration pipeline to (1) always persist locale mapping before content-type mapping, and (2) improve Gutenberg block handling—especially core/media-text—including richer “meaningful HTML” detection and more robust asset lookup.

Changes:

• Post /localeMapper before /createDummyData in the upload-api WordPress controller, and update unit tests to reflect the new request order/behavior.
• Add WordPress core/media-text schema mapping + adjust block dedupe/structure logic to avoid merging it incorrectly with other blocks.
• Improve WordPress parsing in the API service (meaningful HTML detection, cover/media-text media attachment, asset resolution, and asset file writing path changes) and update README instructions.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
upload-api/tests/unit/controllers/wordpress.controller.test.ts	Updates test expectations for new localeMapper-first request order and “locale always posted” behavior.
upload-api/src/controllers/wordpress/index.ts	Sends locale mapper POST before content-type mapper POST.
upload-api/migration-wordpress/libs/schemaMapper.ts	Adds a new schema mapping case for core/media-text.
upload-api/migration-wordpress/libs/extractItems.ts	Extends cross-block dedupe/structure checks to include media-text vs paragraph.
README.md	Adds/adjusts installation and usage instructions for api/upload-api.
api/src/utils/wordpressParseUtil.ts	Adds hasMeaningfulHtmlContent() to detect non-text meaningful markup (media/embeds).
api/src/utils/mimeTypes.ts	Makes extension lowercasing tolerant to undefined inputs.
api/src/services/wordpress.service.ts	Enhances schema creation/formatting for cover + media-text, improves RTE emptiness detection, adjusts asset lookup, and changes asset write/existence logic.

Comments suppressed due to low confidence (1)

api/src/services/wordpress.service.ts:1826

• saveAssetFromUrl now checks fs.existsSync(assetPath) where assetPath is the directory (.../files/<customId>), not the actual downloaded file. This can incorrectly short-circuit downloads (e.g., if the directory exists from a previous attempt, or when the same customId is reused with a different extension), returning an asset ID even though the expected file is missing. Check existence against the full file path (directory + filename) and keep the path variables consistent with where the file is written/lstat’d.

  const assetPath = path.resolve(assetsSave, "files", customId);
  
  // Check if asset already exists
  if (fs.existsSync(assetPath)) {
    return customId;
  }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.