Github user mmiklavc commented on a diff in the pull request:
https://github.com/apache/metron/pull/1219#discussion_r223502181
--- Diff: metron-interface/metron-alerts/package.json ---
@@ -22,17 +22,17 @@
"@angular/platform-browser": "^6.1.6",
"@angular/platform-browser-dynamic": "^6.1.6",
"@angular/router": "^6.1.6",
+ "@ruffle1986/pikaday-time": "^1.6.1",
"@types/bootstrap": "^4.1.1",
"@types/jquery": "^3.3.4",
"ace-builds": "^1.2.6",
"ajv": "^6.5.1",
"angular-confirmation-popover": "^4.2.0",
"bootstrap": "4.0.0-alpha.6",
"core-js": "^2.4.1",
+ "date-fns": "^1.29.0",
"font-awesome": "^4.7.0",
- "moment": "^2.22.2",
"ng2-dragula": "^1.5.0",
- "pikaday-time": "^1.6.1",
--- End diff --
@nickwallen - as an aside, I think this scenario that you've stumbled on
here as it's been laid out shows precisely why the Metron community has
steadily over time requested smaller and smaller PR's as well as more
consistent use of DISCUSS threads when adding dependencies to the project.
Having that pikaday fork is a fait accompli from a large PR that we're now
having to pay the cost of living with.
@ruffle1986 Is there a reason we need to fork a project to get the time
picker support? A couple other options here - Is it possible to either A,
simply remove the time picker component or B, add a separate one that isn't
part of pikaday or C, simply bring the relevant code into Metron so that if we
need to maintain it or make changes we can feely do so? I'd prefer to simply
not have it at all if it's an external dep that's been orphaned.
---
