Nice suggestion. I have copied this request into our feature request database. It will probably take us a wee while to get around to this, so no promises on ETA - but it’s a completely valid suggestion. Thanks!
Hi, will. I have another suggestion. Sometimes, we might use this.app.assets.get(123456); to get the asset. Something like this :
Under the circumstances, if another developer wants to fork my project, the IDs of the assets will change while the IDs in script will not change. This can result in assets not found error.
You shouldn’t really be using asset ids in your scripts. You should use script attributes of type asset or use some other attribute that doesn’t change like asset tags.
@marquizzo to second what Vaios said in another post. You shouldn’t really hardcode asset ids in your scripts. In fact I wouldn’t recommend using asset ids at all. There are several other ways to get assets:
Use asset script attributes to reference specific assets
Use this.app.assets.findByTag(tag) to find a set of assets with a tag
Use this.app.assets.find(name, type) to find an asset by it’s name
Using asset ids will break if you ever fork the project.