ju1ius

Same here with upstream debian buster package. `docker-credential-pass` extracted to `~/.local/bin` ``` $ which docker-credential-pass ~/.local/bin/docker-credential-pass ``` My `~/.docker/config.json`: ```json { "credsStore": "pass" } ``` ```sh $ docker login registry.example.com...

And here's a non-working example with react-final-form: [](https://codesandbox.io/s/w7olkx5n7l) I sort of got it to work by currying the `validateOfferUrl` function, but the behavior is kind of weird......

> OR, you could do array-level validation, and provide the validate prop to FieldArray. That's probably your best solution for now. Thanks for your answer @erikras. Running field-level validation at...

> It would need some additional meta information... Would you consider adding an additional parameter to the validate function ? Something like: ```typescript interface FieldValidationContext { // At least this...

Turns out you _can_ do both: [](https://codesandbox.io/s/mqno35xy7y) The trick is to use an object instead of an array: ```js const validateOffers = (values, form) =>...

@4c0n & @Lyrkan : You might want to look into [webdeveric/webpack-assets-manifest](https://github.com/webdeveric/webpack-assets-manifest). It is actively maintained and looks like it has all the features you need. As an example, the following...

Or you could do: ```twig ``` A bit shorter, but still not perfect. The `html_classes` function seems to be missing some sort of `if($key instanceof \Stringable)` check somewhere...

> Long term, adding `$XDG_CONFIG_HOME` to the resolution path is probably the right fix. And also `XDG_DATA_HOME`. > 1. If `$STEPPATH` exists then use `$STEPPATH`. > 2. If `$XDG_CONFIG_HOME` exists...

Having some kind of error/exception handling would be great indeed! A hook to notify the application for logging purposes (i.e. to sentry, new relic, etc) would also be much welcomed.

I did a bit of basic tests and so far your PR solves one of the big pain points I have with the current macro system: When you have a...