asset/templates: remove fileName field #885
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The fileName field is not needed. The template assets do not need to store this information.
This change is part of work that is on-going to add tests to ensure that targeted assets are not assessed as dirty when read back in without being modified. The problem with the fileName field is that it is not set when the asset is loaded from the state file or from on-disk. This causes road-trip tests that compare a generated asset to a read asset to fail.