Thank you for quick reply.
Yes, indeed this is another way around it.
Going for this method.
P.S thank you and all the peeps of community for this awesome library. Keep it up 
kman4you
1
kman4you
Hey @aesmail, How can I pass this conn struct to my admin in resources.
def create_resources(conn) do
[
profile: [
name: "User Actions",
resources: [
user: [schema: Stakester.Accounts.User, admin: Stakester.Admin.ProfileManagementAdmin, conn: conn],
]
]
]
end
end
In create_resources conn is returning a struct as it should but in admin module of resource
it is showing something like
Stakester.Accounts.User.
I am unable to understand what is going on. How can I my good old conn struct back. I also tried to add conn in resources as you can see but its no use 
If you need anything from my side, please let me know.
Waiting to hear back from you.
0
aesmail
Hey @kman4you, what do you need to do exactly? conn is passed to some functions but not all of them (yet). I’m assuming maybe you need to customize the fields you’re displaying based on some conn-related conditions. In this case, this is currently not supported. However, I could see how this would be useful and it would be a good feature to add.
Originally, most functions were passed the schema module (as you found out). In later versions, conn was also passed to some functions where it made sense. The general idea is, if conn is useful for a certain function, it should probably be passed as an argument.
If this is what you need, you could add it as an issue on GitHub just for reference and a reminder.
I plan on releasing v0.10.0 soon. This might be a quick fix that would make it for the v0.10.0 release.
1
kman4you
Hello @aesmail, thank you for the quick response.
I am trying to make current dashboard user’s management module, (as you can get the idea from example below) so he can perform some actions that he wants like changing his name or email and other stuff like that and I need to get the current_user which is in the conn -> assigns. This is what I am trying to do.
P.S I got your point that currently it is not possible, so I am adding an issue on GitHub as a reminder and waiting for the next release.
profile: [
name: "User Actions",
resources: [
user: [schema: Stakester.Accounts.User, admin: Stakester.Admin.ProfileManagementAdmin, conn: conn],
]
]
0
aesmail
If you want to limit access to some resources (showing only resources for a specific user for example), you could actually use custom queries. You could filter the results based on current_user and show that instead of the default result (all users).
Would this work?
1
kman4you
Yes, for now this will work but the other solution will be better if we can just pass the conn so this process can be simplified.
1
aesmail
Yeah I’ve been meaning to fix that but things got a bit messy locally trying the demo with the unreleased v0.10.0. I’ll try to get it back up as soon as possible.
1
jkbbwr
FYI creating a new item that has a many-to-many relationship fails with
protocol Phoenix.HTML.Safe not implemented for #Ecto.Association.NotLoaded<association :xyz is not loaded> of type Ecto.Association.NotLoaded (a struct). This protocol is implemented for the following type(s): Decimal, Phoenix.LiveView.Component, Phoenix.LiveView.Rendered, Phoenix.LiveView.Comprehension, Phoenix.LiveComponent.CID, Integer, NaiveDateTime, Date, Atom, BitString, Phoenix.HTML.Form, Time, Tuple, Float, DateTime, List
1
