Bug #23215
Keep original plugin names in webpack plugin bundle
Status:
Closed
Priority:
Normal
Assignee:
Category:
JavaScript stack
Target version:
Pull request:
Fixed in Releases:
Found in Releases:
Description
Currently the webpack config is shortening the name of the js bundles for plugins. E.g, foreman_remote_execution becomes remoteexecution, and so on.
This becomes hard to deal with when we want to figure out which plugin contains the source for each bundle.
Related to #23147
Associated revisions
Refs #23215 - 2.3 compat. for webpack in plugins script
.match? was only introduced on 2.4, therefore it's failing to run
on 2.3 and test pipelines for plugins with webpack & Ruby 2.3 fail
History
#1
Updated by The Foreman Bot over 4 years ago
- Assignee set to Daniel Lobato Garcia
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5432 added
#2
Updated by Anonymous over 4 years ago
- Legacy Backlogs Release (now unused) set to 330
#3
Updated by Anonymous over 4 years ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset 90db5e364ff209f093c64849e21d3362644367f8.
#4
Updated by The Foreman Bot over 4 years ago
- Pull request https://github.com/theforeman/foreman/pull/5459 added
#5
Updated by The Foreman Bot over 4 years ago
- Pull request https://github.com/theforeman/foreman/pull/5488 added
Fixes #23215 - Keep original names in webpack bundle
Currently the webpack config is shortening the name of the js bundles
for plugins. E.g, foreman_remote_execution becomes remoteexecution, and
so on.
This becomes hard to deal with when we want to figure out which plugin
contains the source for each bundle.
Related to #23147
Conflicts:
app/registries/foreman/webpack_assets.rb
script/plugin_webpack_directories.rb