Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are two updates here.
The first resolves a number of issues related to Elixir 1.14 and an upgrade of ex_doc. It changes the use of "use Bitwise" and eliminates the use of get_env at compile time. It eliminates the use of "use Mix.Config", anticipates the deprecation of Logger.warn in 1.15, and fixes some problems running test and mix docs. (I still can't run tests because it doesn't like me running "MIX_ENV=test mix ecto.create", but at least the compile warnings are resolved.)
The second update resolves dialyxir warnings from two sources. I ran it against the project itself and tried to resolve those errors including resolving some suppressed errors, but I also ran it against InfinityOne where I know it generates a lot of warnings of a repetitive type. The latter effort triggered the mass of changes in the responders, where the arity 1 functions inserting an empty map generally didn't help, because the arity two functions almost all require some specific keys in the map, so will fail with a FunctionClauseError, where now if you call the arity 1 it should fail on compile.
I suggest reviewing the two commits independently.