Vendor assets not found if shortName != package name #137
Unanswered
datashaman
asked this question in
Q&A
Replies: 1 comment
-
@datashaman You can add the correct name in the methods, isn't that the same? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed that the readme suggests that we can publish vendor assets using a variation of this:
The assets are being tagged with the shortName instead of the package name, which is fine if those two are the same. But not if they are different. For example a package named
laravel-translators
has a shortName oftranslators
, which means the documented way of publishing the vendor assets doesn't find anything.This does not work:
This works:
I think it's a bit weird having a very generic tag of
translators-config
be generated and suggest that the code be changed to match the documentation. PR incoming.Beta Was this translation helpful? Give feedback.
All reactions