fix: resolve nested relations in content blocks properly

[edodusi]

Fix nested relations resolution in Storyblok SDK

Pull request type

Internal ref: #13985

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Other (please describe):

How to test this PR

1. Create a story with nested relations (e.g., an event_slider with spots containing event_type relations)
2. Request the story with resolve_relations including both direct and nested relations:

const response = await Storyblok.get("cdn/stories/your-story", {
  version: "draft",
  resolve_relations: [
    "event.event_type",
    "event_slider.spots"
  ]
});

3. Verify that nested relations (like story.content.body[0].spots[0].content.event_type) are properly resolved to objects instead of remaining as UUIDs

What is the new behavior?

• Fixed nested relations resolution by improving the field pattern matching in _insertRelations
• Added support for resolving relations at any nesting level within the content tree
• Added unit tests to verify proper resolution of nested relations
• The fix ensures that all relations are properly resolved, regardless of their position in the content structure

Other information

This fix addresses an issue where nested relations (relations within component arrays or nested content) were not being properly resolved, remaining as UUIDs instead of being replaced with their corresponding objects. The solution improves the relation resolution logic to handle relations at any nesting level while maintaining backwards compatibility with existing functionality.

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/storyblok-js-client@903

commit: 1cbb6cf

[roberto-butti]

I tested with the original use case and is fine, now.
I tested also some different scenario like: nested relations and nested duplicated relations. So the applied changes covers more scenarios than the current version

[github-actions]

🎉 This PR is included in version 6.10.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀