Assets: move the remaining runtime path reads onto IContentSource
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- backend, embedded-iot
Research direction
Start with one independent area, such as GameRuntime.cs catalog lookup or the project settings index in ProjectSettingsLoader.cs, and trace how runtime path reads use IContentSource. The issue names additional areas including asset metadata, the type manifest, UI assets and the window icon; editor only paths should stay unchanged. Done means runtime assemblies contain no File. or Directory. calls outside FileContentSource and editor only code, with desktop export and play unchanged.
Written by the indexing model from the issue text.
Description
Current State
Besides OAP, many runtime reads assume real paths: GameRuntime.cs:134-142 (catalog lookup), AssetDatabase.cs:111-125 and AssetDatabase.Catalog.cs:212, ProjectSettingsLoader.cs:102-108, 235-238, RuntimeAssetLoader.cs:219-231 (meta), PrecastAssemblies.cs:20-22 and TypeRegistry.cs:254-266 (type manifest), the UI brick (UiManagerFactory.cs, UiDocumentAsset.cs, UiStyleSheetAsset.cs, UiImageResolver.cs, UiFontResolver.cs) and the window icon. Each area is independent: one small PR per area.
Tasks
- Catalog and asset database
- Project settings index
- Runtime asset meta
- Type manifest (precast assemblies and type registry)
- UI brick documents, style sheets, images and fonts
- Window icon
- Editor-only paths stay as they are
Acceptance Criteria
- No
File./Directory.calls in runtime assemblies outsideFileContentSourceand editor-only code - Desktop export and play unchanged
Related
- Android plan task A8 · seniority Jr · mergeable now (.NET 10)
- Depends on: #242
- Platform roadmap: #100
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 48m
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MASS4ORG/Turian
-
c:docs p:high size:S t:docs
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
c:assets p:low size:XS t:task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
c:engine c:scripting p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
c:assets c:platform p:low size:M t:feature
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
c:platform c:scripting p:low size:M t:task
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Fallout-build/Fallout#708 ·
Maintainers usually reply within 5 days
-
bug next version
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Rem0o/FanControl.Releases#4220 · 1 comment ·
-
area:repo audit:approved audit:auto priority:P3
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-core#8771 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nkdAgility/azure-devops-migration-tools#3217 ·
Maintainers usually reply within 1 day