You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the great things about Xcode's xcassets Import feature is if you import from a folder it will maintain the directory structure the images were in. Does Blade do this automatically?
The text was updated successfully, but these errors were encountered:
It will actually just "stalk" the existing folder structure. So, anything with a Contents.json (typically image catalogs) will be a valid output path for Blade.
If paths are already defined in an existing Contents.json -> Blade will use those by default.
If not, then the file format will be output by blade's own definitions, here's such an output:
Here's a sample mapping (Bladefile), I took the liberty of commenting these for you:
blades:
- source: assets/app-icon.png # this is the source asset filemount: SnappyScan/Images.xcassets/AppIcon.appiconset # this is where the generated files would be dumped intocontents: true # generate a new catalog, doesn't matter what's already in there
- source: assets/splash-icon.pngmount: SnappyScan/Images.xcassets/SplashIcon.imagesetcontents: true
So you see, Blade will work with what's already there, and not generate its own tree structure. This is by design.
Nevertheless, this project is open to other ideas - bring them in if you have them.
One of the great things about Xcode's xcassets Import feature is if you import from a folder it will maintain the directory structure the images were in. Does Blade do this automatically?
The text was updated successfully, but these errors were encountered: