Claude recommended to tag critical e2e tests with `e2e_smoke` and run the full e2e suit not in PRs but maybe in another callback like "before deploy".
So easy with Elixir testing system 🔥
Lovin #elixirlang . I wanted to experiment with E2E testing using github.com/germsvel/pho... and the playwright adapter.
My concern with e2e tests are that are expensive so I asked AI what I can do to mitigate it.
Holy shit. Thanks. From 4 minutes to 34 seconds 😂
Could Grok, the Ai of Elon provoking CANCER to the people of Memphis?
youtube.com/shorts/jBJxX...
Thanks! I'll take a look
I think I do. Do you see something I can improve github.com/andresgutgon...
Man dialyzer is super slow. I wish native Elixir types arrive soon
Grok saying openly that Trump is a pedophile
Got to admit. Grok was savage here 😂
I just discovered Ash code interfaces :cheff_kiss:
@zachdaniel.dev I linked to the magic link controller here. You asked for it last time we talked about this : )
My first impressions with Ash and Ash authentication
andres.fika.bar/my-first-imp... My experience using the Ash framework for the first time. #elixirlang @ash-hq.org
Without almost no modification, you can use @ash-hq.org auth package to build a multi-account OAuth connection.
Now this user can connect to the app with 2 different Google accounts and one Github account. Really nice. I'll publish the code changed to make default auth work this way. #elixirlang
I'm a big fan of not doing that xD
This is all the magic-link workflow
github.com/andresgutgon...
What do you think? Can it be done in a more Ashy way?
Oh! It works. This is beautiful
The level of compression here is amazing
✅ Register/login with password
✅ Register/login with magic link
✅ Register/login with GitHub
✅ Register/login with Google
✅ Change password flow
✅ Remember me cookie
✅ `return_to` session redirect after login
Is this a nice way of splitting actions in an @ash-hq.org resource? Didn't try yet but just with all the auth stuff, my user resource is huge
Is this works would be fantastic
Happy to learn. But starting from Phoenix team generated auth would you say is safe? If the answer is yes the same could be done in Ash.
It would make even easier the migration from vanilla auth to Ash auth if the controller paths and names are the same.
I trust your design I'm just following it. That's the point of this digging. But the UI is mine and mine alone xD
So far everything clicks perfectly
Shit, did i say that? : / not my point at all.
But i think these magic routes hurt more than help ash auth adoption. Would be better the Phoenix approach. We already discussed this has the tradeoff of delegating security on the devs. But if they're using Ash auth in their controllers i think is ok
This is for registration and login. Is the right way?
bsky.app/profile/andr...
So far super happy with Ash actions bsky.app/profile/andr...
I'm using Ash actions. Otherwise i lost my weekend 😂
Not migrated yet. I'll do a blog post and link to the repo. Happy for your feedback when done!
This is what the AI did. But I can plug here shadcn with React or plain old CSS or Liveview.
The point is that's mine and mine alone. At the end of the day in a real project, working with a product team will be a brand identity to be followed. You're not going to go with Ash auth almost never.
But if my requirements change I can easily change.
This is `submit_form` method inside helpers
Easy to change, use Ash Form, do remember me for login and register and also handler `return_to`. Not bad for 20 LOC
This is my register old boring controller
Two things here
a) The view is mine and I can style as I please
b) Yes, this has an abstraction in AuthHelpers that use Ash under the hood.
All code for `new` and `create` is exactly the same for me so I abstracted.
Ash auth view abstractions are all liveview super complex to follow. Example of signin.
This uncessarily complex because it has to cover all type of auth strategies but maybe you just want magic link.
Is impossible to fully change to the pixel this UI
