关于Autodesk Forge翻译器误选rootFile的技术咨询

Absolutely—this sounds like a clear bug in the translation service's root file selection logic, and here's why:

The Core Issue #

When you explicitly specify a root file (assy.sldasm), the service should prioritize exact filename matches over any partial matches or lexical sorting. The fact that it’s defaulting to an assy.sldasm—a lexically earlier file that only partially overlaps with your target filename—directly violates the expected behavior of honoring user-specified inputs.

Problem Breakdown #

Your example zip structure makes this issue crystal clear:

example.zip
├── part1.sldprt
├── part2.sldprt
├── an assy.sldasm <-- Incorrectly selected by the translation service
└── assy.sldasm <-- Your explicitly specified rootFile

When you submit a translation request with assy.sldasm as the root, the service should follow this logical flow:

1. First scan the uploaded zip for an exact filename match to your provided rootFile value.
2. Only fall back to alternative selection logic (like lexical sorting or partial matching) if no exact match exists.

Instead, it’s using partial matching combined with alphabetical order to pick the wrong file—this is not intended behavior for a service that accepts explicit root file parameters.

Steps to Validate & Report the Bug #

To formalize this as a bug and get it fixed:

• Reproduce the issue with your test files (you mentioned you can share them—this will be critical for the service team to debug the root cause).
• Cross-check the service’s documentation: if it explicitly states that exact matches are prioritized for rootFile inputs, this behavior directly contradicts the documented functionality.
• Submit a bug report to the service team including:
  • The full structure of your test zip (or the zip file itself).
  • The exact request parameters you used (including the rootFile value).
  • The manifest output showing the incorrect root file was selected.

内容的提问来源于stack exchange，提问作者Karl EK