-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: subscription dsl #97
Conversation
@zachdaniel I tried to create a test case for the current behaviour before trying to move the code into the dsl but I got a bit stuck. I copied stuff from https://github.com/absinthe-graphql/absinthe/blob/master/test/absinthe/execution/subscription_test.exs and https://github.com/ash-project/ash/blob/main/test/notifier/pubsub_test.exs but I can't see any messages. I think I'm missing something, Maybe you can give me a hint to get unstuck. Thanks |
Will take a look tomorrow 👍 |
The issue doesn't jump out to me immediately...the first step might be to add a custom notifier and make sure notifications are going out at all. |
429c0b2
to
bb1615b
Compare
bb1615b
to
771072d
Compare
d022389
to
82f3d90
Compare
82f3d90
to
3b6bbde
Compare
d7f1a1e
to
4225d9d
Compare
27d8d37
to
7c5d504
Compare
517ede8
to
4a2a359
Compare
6bd432b
to
9484723
Compare
build_read_one_query
|> Ash.can(....)
|> case do
{true, query} ->
if query.authorize_results == [] && we_can_tell_the_record_matches(record, query.filter) do
just load any necessary data on the record we got
else
do a read one w/ the load
end
end Can you explain what for |
For evaluating the filter against the record, I'd use something like |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀 lets gooooooooo.
Awesome work!
Feel free to merge at your convenience :) |
Co-authored-by: Zach Daniel <zach@zachdaniel.dev>
@zachdaniel accepting your suggestion dismissed your approval, now merging is blocked again 😅 |
Contributor checklist