A PR for supporting keywords on the default handler is welcome. :)
On Sat, Apr 29, 2023 at 00:43 Christopher Keele
wrote:
> I can second that this has caught me off-guard before as well, and keyword
> list support would be a welcome addition.
>
> > It can be confusing if folks then use the
I can second that this has caught me off-guard before as well, and keyword
list support would be a welcome addition.
> It can be confusing if folks then use the direct Erlang APIs.
I think this could be circumvented for now by only describing the proposed
keyword list support in the boot
Looks like it works with any data structure - producing improper lists
On Friday, April 28, 2023 at 2:55:34 PM UTC+2 Daniel Kukula wrote:
> I accidentaly used Keyword.pop instead of Keyword.take and my code did not
> catched it because you can append a tuple to a list - is this expected
>
I accidentaly used Keyword.pop instead of Keyword.take and my code did not
catched it because you can append a tuple to a list - is this expected
behaviour ?
iex [14:50 :: 1] > [1,2] ++ {3,4}
[1, 2 | {3, 4}]
iex [14:50 :: 2] > {3,4} ++ [1,2]
** (ArgumentError) argument error
I am wondering if we should allow keyword lists in those cases instead but
it can be confusing if folks then use the direct Erlang APIs.
On Fri, Apr 28, 2023 at 3:02 PM lostko...@gmail.com
wrote:
> Trying this again as my last 3 answers got deleted:
>
> For example here:
>
> config :logger,
I think `mix test --listen-on-stdin` might meet your use case. From the
docs:
--listen-on-stdin - runs tests, and then listens on stdin. It will
re-run tests once a newline is received. See the "File system watchers"
section below
I setup an alias for this: alias mtl="PORT=4006 mix test
Trying this again as my last 3 answers got deleted:
For example here:
config :logger, :default_handler, config: %{
file: ~c"system.log",
filesync_repeat_interval: 5000,
file_check: 5000,
max_no_bytes: 10_000_000,
max_no_files: 5
}
... as described in
