What is "Asset Pipeline: Implemented accessor for saving data to .meta files"

Title.

Cant find any information about this.

Maybe an easier way to write stuff to the .meta’s userData? Right now you have to grab the assetimporter and do a bunch of wrangling.

1 Like

Hi!
This is my release note :slight_smile:
So, it should not have been a public note, but here we are!

The issue that it addressed was that all over the codebase we had misc. string manipulations to edit some YAML which would result in the contents of a .meta file. When the new AssetOrigin feature (for the Asset Store) needed to add a new optional field to the .meta files, we went ahead and took that opportunity to tidy up the codebase and have a single class that would allow for the creation of the contents of a .meta file.

Instead of having code sprinkled throughout the codebase that was appending strings in a (hopefully) YAML format, we now go through a single point of entry where we can clearly define what fields should be present in the .meta file, and do a final call to generate the string that represents the .meta file.

Its not a user facing change, but more of a code cleanup change.

3 Likes