Klemen Sever

@peterdalydickson I got the same problem but, as explained in the below link, the problem was that there was a "-" character which was unicode instead of the default ASCII...

As mentioned on #1135, this bug still occurs on 0.15.0. I'm pretty sure, I've pinponted the issue to the `PHX_HAS_SUBMITTED` that remains undefined even after a submit. It requires a...

Hi @justincjohnson, as mentionned in #1135, I fixed the issue by setting the action to `:insert` instead of `:validate`. In your sample project, I see you're using `Ecto.Changeset.apply_action(changeset, :validate)` when...

Hm I see. Indeed, I tried `drop-*-as-needed` but I got gaps when zooming in. On the other hand `coalesce-*-as-needed` works quite well but then I get one feature id used...

Hi @jorbs :) Thanks for opening this issue. Your point is valid. We have a similar logic in our own system but also additional logic (cleanup some session values, reset...

I'm not against adding it to the library 😄 OAuth2 flows aren't easy and logout implies multiple levels of logout: Application level (e.g. your elixir app), Auth0 level, Social sign-in...

> Should we just close this dangling PR? I'm keeping it here as a reminder for when I do the next update, I'll probably fix & merge it. If I...

Hi @hexedpackets, thanks for your other pull-request :) I'd be happy to remove the call to `/userinfo` under two conditions: - there's a documentation on auth0 website confirming that the...

Hey :) This evidence sounds reasonable indeed. Let's try this. Let's create the PR and I'll do some tests on a live auth0 system to check if I always get...

Thanks for the pull request @hexedpackets 😻 From the Auth0 documentation (and quote of the corresponding text, emphasis mine): https://auth0.com/docs/manage-users/organizations/configure-organizations/invite-members#configure-the-uri > The route in your application must accept `invitation` and...