1.5 KiB
ID, Type, Status, Priority, Labels, Created, Updated, Related
| ID | Type | Status | Priority | Labels | Created | Updated | Related | |||
|---|---|---|---|---|---|---|---|---|---|---|
| ISSUE-001 | Issue | Backlog | Medium |
|
2025-04-22 | 2025-04-22 |
[ISSUE-001]: Source file naming rules from JSON are not respected
Description
The tool is not correctly applying the "Source file naming rules" defined in the JSON presets. Specifically, the "base Name index" and "Map type index" values within the source_naming section of the preset JSON are not being respected during file processing.
Current Behavior
When processing assets, the tool (observed in the GUI) does not use the specified "base Name index" and "Map type index" from the active preset's source_naming rules to determine the asset's base name and individual map types from the source filenames.
Desired Behavior / Goals
The tool should accurately read and apply the "base Name index" and "Map type index" values from the selected preset's source_naming rules to correctly parse asset base names and map types from source filenames.
Implementation Notes (Optional)
(Add any thoughts on how this could be implemented, technical challenges, relevant code sections, or ideas for a solution.)
Acceptance Criteria (Optional)
(Define clear, testable criteria that must be met for the ticket to be considered complete.)
- Processing an asset with a preset that uses specific
base_name_indexandmap_type_indexvalues results in the correct asset name and map types being identified according to those indices. - This behavior is consistent in both the GUI and CLI.