Skip to content
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

Memoize current_user in actions #508

Merged
merged 2 commits into from
Feb 19, 2023
Merged

Memoize current_user in actions #508

merged 2 commits into from
Feb 19, 2023

Conversation

paulcsmith
Copy link
Member

Still need to do this in ApiAction too

@paulcsmith
Copy link
Member Author

paulcsmith commented Apr 25, 2020

Memoize does not work with a "Nil". Opened an issue on Lucky to support this use case

luckyframework/lucky#1119

@@ -25,7 +25,8 @@ abstract class BrowserAction < Lucky::Action
expose current_user

# This method tells Authentic how to find the current user
private def find_current_user(id) : User?
# The 'memoize' macro makes sure only one query is issued to find the user
private memoize def find_current_user(id) : User?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can just set this type to User. If it's nil, it just won't memoize. I saw you opened the issue already for that, but until we have that in, this could be a small win.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand. The User can be nil so I can't change the return type to not have nil.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The memoize right now doesn't allow you to specify a union like User? https://github.com/luckyframework/lucky/blob/master/src/lucky/memoizable.cr#L21 so this should throw a compile time error.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah this does throw an error so I opened the issue to add support. I’m not sure how we’d get a quick win by setting it to User because that also won’t compile. I am quite tired so maybe just being dense haha

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that memoize supports taking args and having a nil value, I think this is fine. 😄

@jkthorne
Copy link
Contributor

when there is a query cache will this make sense?

@paulcsmith
Copy link
Member Author

@wontruefree It still might be good so that it doesn't log a cache hit, but the performance gain would be very minimal once the query cache is shipped

@jkthorne
Copy link
Contributor

I am curious because memorization like this will cause more memory usage for minimal performance with query caching. This might be worth revising when query cache is added.

@paulcsmith
Copy link
Member Author

Good idea! We can revisit once query caching is added 👍

@jwoertink
Copy link
Member

Just dropping some notes here. Currently neither of these updates would compile. Bug filed here luckyframework/lucky#1396

Copy link
Member

@jwoertink jwoertink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, it took a few years, but this change actually works now 😆

@jwoertink jwoertink merged commit 16d9ed1 into main Feb 19, 2023
@jwoertink jwoertink deleted the pcs/memoize-current_user branch February 19, 2023 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants