Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PackageExport: remove template Upset file #47

Open
niezbop opened this issue Jan 5, 2018 · 0 comments
Open

PackageExport: remove template Upset file #47

niezbop opened this issue Jan 5, 2018 · 0 comments

Comments

@niezbop
Copy link
Member

niezbop commented Jan 5, 2018

The need to maintain both the packageexport.asset and the templateUpset.xml in a project is cumbersome and should be streamlined, by putting the depencies and the configuration into the asset directly.

To do this, we need to:

  • Extract the custom fields we use in the UpfileEditor.cs to keep things DRY
  • Introduce the dependencies and the configuration in the scriptable object

What needs to be considered:

  • Backwards compatiblity: any system relying on the packageexport.asset would fail if it relies on an template Upset. Should we then accept breaking changes (after all we're still in beta), or provide some sort of migration mechanism, perhaps relying on an Asset Processor?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant