Use mintbasev2.near instead of mintbase2.near

[rubenmarcus]

PR Type

enhancement, documentation

---

Description

• Replaced hardcoded contract addresses with dynamic values from mbjs.keys.mbContractV2 in mock data and tests.
• Updated @mintbase-js/sdk dependency to version 0.6.0-beta-prerelease.1.
• Updated example usage in README to reflect new contract address dynamic.mintbasev2.near.

---

Changes walkthrough 📝

	Relevant files
Enhancement	dynamicNftMetadata.mock.ts Use dynamic contract addresses in mock data                            packages/data/src/api/dynamicNftMetadata/dynamicNftMetadata.mock.ts Replaced hardcoded contract addresses with dynamic values from mbjs.keys.mbContractV2. Updated metadataId and contractAddress fields accordingly. +9/-7      dynamicNftMetadata.test.ts Use dynamic contract address in tests                                        packages/data/src/api/dynamicNftMetadata/dynamicNftMetadata.test.ts Replaced hardcoded contract address with dynamic value from mbjs.keys.mbContractV2. +3/-3
Dependencies	package.json Update @mintbase-js/sdk dependency version                              packages/data/package.json Updated @mintbase-js/sdk dependency to version 0.6.0-beta-prerelease.1. +1/-1
Documentation	README.md Update example usage with new contract address                      packages/data/src/api/dynamicNftMetadata/README.md Updated example usage to reflect new contract address dynamic.mintbasev2.near. +1/-1

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[mintbase-codium-pr-agent]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[mintbase-codium-pr-agent]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Validate or provide a fallback for critical variables to prevent runtime errors Ensure that the mbjs.keys.mbContractV2 is properly validated or has a fallback since it's critical for constructing metadataId and contractAddress. packages/data/src/api/dynamicNftMetadata/dynamicNftMetadata.mock.ts [6-8] -metadataId: `dynamic.${mbjs.keys.mbContractV2}:deadbeef2`, -contractAddress: `dynamic.${mbjs.keys.mbContractV2}`, +const contractKey = mbjs.keys.mbContractV2 || 'defaultContractKey'; +metadataId: `dynamic.${contractKey}:deadbeef2`, +contractAddress: `dynamic.${contractKey}`, Suggestion importance[1-10]: 9 Why: Validating or providing a fallback for critical variables prevents potential runtime errors, which is crucial for robust code.	9
Best practice	Use a constant for repeated string literals to enhance maintainability and reduce errors Consider using a constant for the domain prefix 'dynamic.' to ensure consistency and reduce the risk of typos in multiple uses. packages/data/src/api/dynamicNftMetadata/dynamicNftMetadata.mock.ts [6-8] -metadataId: `dynamic.${mbjs.keys.mbContractV2}:deadbeef2`, -contractAddress: `dynamic.${mbjs.keys.mbContractV2}`, +const DOMAIN_PREFIX = 'dynamic.'; +metadataId: `${DOMAIN_PREFIX}${mbjs.keys.mbContractV2}:deadbeef2`, +contractAddress: `${DOMAIN_PREFIX}${mbjs.keys.mbContractV2}`, Suggestion importance[1-10]: 8 Why: Using a constant for repeated string literals enhances maintainability and reduces the risk of typos, which is a best practice in coding.	8
Maintainability	Use a more flexible version specifier for dependencies to ease future updates Locking the version of '@mintbase-js/sdk' to a specific pre-release might cause issues with future updates. Consider using a more flexible versioning strategy. packages/data/package.json [24] -"@mintbase-js/sdk": "=0.6.0-beta-prerelease.1", +"@mintbase-js/sdk": "^0.6.0-beta", Suggestion importance[1-10]: 8 Why: Using a more flexible version specifier for dependencies allows for easier future updates and reduces the risk of compatibility issues.	8
	Maintain consistency in string construction for readability and maintainability Use template literals consistently for contractAddress to maintain code consistency and readability. packages/data/src/api/dynamicNftMetadata/dynamicNftMetadata.test.ts [21] -contractAddress: 'dynamic.mintbasev2.near', +contractAddress: `dynamic.${mbjs.keys.mbContractV2}`, Suggestion importance[1-10]: 7 Why: Maintaining consistency in string construction improves code readability and maintainability, which is important for collaborative development.	7

[sainthiago]

🧙‍♀️