User tests: Successful: Unsuccessful:
Pull Request for Issue # .
Kinda replaces #36906 (no FA upgrade to v6)
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_media NPM Change JavaScript Repository |
Labels |
Added:
NPM Resource Changed
?
|
I have tested this item
Thank you
Is it intentional that the joomla.asset.json files no longer have a version hash?
The hash is not generated automatically per npm ci
, you need to run specifically npm run versioning
. (the reason is because for development having to invalidate this hash every time you apply some changes in any of the css/js would be an extra step which will be a way slower workflow)
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-03-17 19:55:20 |
Closed_By | ⇒ | bembelimen | |
Labels |
Added:
?
|
Thx
I can confirm that the deprecation notices have now gone
Is it intentional that the joomla.asset.json files no longer have a version hash?Commented on the code where there is an error in your math