Manage existing image files
- Dominant language
- Go
- Stars
- 816
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Hi @jondot
thank you for this project! This is something I've always thought about, but your current implementation is even better than my dreams :)
I see some space of possible enhancement in the way file names are handled: currently as I understand it is not possible to use wildcards, and image PNGs must be mapped 1-to-1 with imagesets in asset catalogs. I wonder if you have any thoughts on how to handle wildcards or file name pattern matching in Bladefiles. A different approach could be to auto-generate Bladefiles from the content of a folder or an asset catalog.
Cheers,
ac
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files, tests, or entry points. First inspect the existing Bladefile filename-mapping and asset-catalog generation flow, then clarify whether wildcard matching or automatic Bladefile generation is wanted before defining completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100