Griffin Byatt
Griffin Byatt
Hi @newdayrising! It looks like you misunderstood my suggestion. It is possible to retire specific versions of libraries on Hex.pm. My recommendation is that, once a new release is made,...
@joshprice - Yes, it is.
@joshprice - No problem! If you run the command with the `-v` flag (e.g. `mix sobelow -v`), there is a link to this issue. I could do a better job...
@joshprice - I will update the original issue to include additional information in the next week or so. But, at a high level (for anyone reading this in the mean...
> Correct me if I am wrong, but this issue is found in any User model exposing a path to update parameters. This is correct! Typically, you would avoid this...
@smpallen99 It was only an example of a possible field that you would generate a value for, not one that necessarily exists.
@seanculver - As long as you aren't using `coherence_schema`, `coherence_fields`, or the default `changeset` & associated endpoints, you should be fine as far as this issue is concerned.
@seanculver - No problem! I haven't looked much into those issues, but I believe they are false-positives. It looks like it's flagging a bunch of `String.to_atom` calls used in some...
Hi @newpain01! To my knowledge, these issues are not resolved. Avoiding these issues is difficult if you are fully using this library, but if you are only using bits of...
I agree that some kind of macro expansion would be nice. Though, I think operating on beam files directly would end up being a worse experience, since you may lose...