-
Notifications
You must be signed in to change notification settings - Fork 140
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
define asset-type properties #21
Comments
Any takers on this? |
Yeah… it feels like we've covered this many times… my only concern is if we reserve certain keys, what should they be? Packages probably shouldn't be shipping un-compiled (scss, less, coffeescript assets) because they're not immediately useful to anyone. Perhaps we aim for anything that can be directly linked from a HTML document. That is:
|
I agree that it would be useful to have more granular information about assets. @benschwarz, I disagree with this statement:
There are very good use cases for compiling scripts, modules, scss, etc. in the context of the application's source code. Therefore, I wouldn't limit the list to compiled assets. |
@unscriptable Ok. Lets not have that argument in this thread though ⛵ |
Closing here and moving to new issue #47. |
for example:
styles
,scripts
,fonts
,images
. without these, it makes life difficult for tools to have any useful information that defines the component contentsThe text was updated successfully, but these errors were encountered: