Added a description of a known issue

[BuelieR]

Added a description of a known issue.
Using the official mapping makes it impossible to instantiate Identifier, but most tutorials nowadays are based on the YARN mapping and do not explain this in detail.

[netlify]

✅ Deploy Preview for nimble-elf-d9d491 ready!

Name	Link
🔨 Latest commit	dd1d7a2
🔍 Latest deploy log	https://app.netlify.com/projects/nimble-elf-d9d491/deploys/698adcf5ce3c68000831a7da
😎 Deploy Preview	https://deploy-preview-491--nimble-elf-d9d491.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[its-miroma]

What about Identifier.fromNamespaceAndPath()?

[ekulxam]

Identifier being abstract is not caused by mojmap. Mappings only change the name of the class, not the access modifiers or the function of the class. Additionally, the modern fabric docs are in mojmap and correctly use Identifier.fromNamespaceAndPath, which is Identifier.of in yarn. Notice how both methods perform the same function (although they have different names due to mappings), and Identifier is still abstract.

[its-miroma]

most tutorials nowadays are based on the YARN mapping

while that might have been true back in 2024, the docs now are fully migrated to Mojmap