schoofseggl
schoofseggl
Have you noticed the plunk above? It's a small angular filter calls the shortEn humanizer (took it from your website)
Vanilla plunk: https://plnkr.co/edit/KYn1iltDBl4viEDQE4Ig
Arg, forgot to save the plunk. New one: https://plnkr.co/edit/WwL30XZbp8kffm5EN22I?p=preview For 7200 seconds I get with round, largest 2: 2 hours with round, largest 1: 2 hours Which is correct obviously...
At least for the issue I reported initially I can confirm it's fixed, thanks :)
I need to add the information that even with the simple pattern "^.*$" ng-pattern-restrict makes it impossible to type a leading sign. In the browser console I get the following...
Hi @AlphaGit Tested with Chrome "Version 55.0.2883.87 m (64-bit)" and ng-pattern-restrict version 0.2.2. Regards Andreas
Just a side-remark: It would be helpful for me if there was a possibility to dynamically disable ng-pattern-restrict (e.g. I would do so for input type=number). Something like `ng-pattern-restrict ng-pattern-restrict-inactive=true`...
You're right, it sounds weird to use the directive and switch it off. I fully agree. But as you accepted the non-working ".*" pattern on input number fields as a...
I tested it, I can now user the .* pattern on input fields. Thanks a lot for your support! I just noticed that I still get the exception on number...
I can confirm this bug. In Directory.Build.Props we set the property `IsTestProject` to all test projects: ``` False True ``` But during the run it was analyzed even though we...