Skip to content
This repository was archived by the owner on May 9, 2025. It is now read-only.

Conversation

@jzapdot
Copy link
Contributor

@jzapdot jzapdot commented Feb 21, 2020

Summary

I'm not sure if this would be useful to you, but we found after some use that we didn't like developer description as a feature because it would result in long strings being shipped with a build and rely more on the name of the SO asset to be self-documenting (or outline general usage of SO assets elsewhere). This PR removes the developer description type and adjusts its usage accordingly across the library.

Feel free to close this if not useful for you.

* Removed the developer description field and adjusted inspector/drawer usage accordingly.
@DanielEverland
Copy link
Owner

I've thought about this myself, I never really used them when working on my own game. Seeing as they're broken in 2019.3, and I'm way too busy to fix it at the moment, I think this might be a good time to say goodbye to descriptions.

You could argue that if the asset isn't understandable simply from its name, it's probably too complex, and should probably be split into multiple modules.

@DanielEverland DanielEverland merged commit 8d498bc into DanielEverland:master Feb 22, 2020
@DanielEverland
Copy link
Owner

Thanks for the great PR, as always :)

@DanielEverland DanielEverland added this to the Release 1.6.5 milestone Feb 22, 2020
@jeffcampbellmakesgames
Copy link
Contributor

You could argue that if the asset isn't understandable simply from its name, it's probably too complex, and should probably be split into multiple modules.

Absolutely, totally agree with you on that end.

Thanks for the great PR, as always :)

Glad to help!

@Monsoonexe
Copy link

I understand, but I'm sad to see this feature go.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants