last_name | Name Suggester

That's related to some unexpected issue related to the use of --nomultiline or IRB.conf[:USE_MULTILINE] = false inside .irbrc file.

Similar issue with the hack

To avoid that issue, you can just skip using --nomultiline option, when launching your rails console.

You need to pass the path for the controller, not just the object.

The second join statement specifies to join on s.book_id = b.id where s is sales and b is books. However, a record in the books table will not be returned unless it has a corresponding record in the sales AND customers tables, which is what a left join does by definition https://www.w3schools.com/sql/sql_join_left.asp. put another way, this query will return all books that have been purchased by at least one customer (and books that have been purchased multiple times will appear in the results multiple times).

Your searchMembers method returns the filtered results directly. While your code

You mean to log the string once the test done?

Well you have to use nested callbacks to make it in your desired order.

So after first id in db check is done, proceed for next id check inside of the first id callback.

Instead of case_when, it may be more appropriate to use if () else (). Also, when your prettyCheckboxGroup is unchecked, the value is NULL, and you need to handle that. Try this

Gin gonic uses the package github.com/go-playground/validator/v10 to perform binding validation. If the validation fails, the error returned is a validator.ValidationErrors.

This is not mentioned explicitly but here in Model binding and validation it states:

Gin uses go-playground/validator/v10 for validation. Check the full docs on tags usage here.

That links to the go-playground/validator/v10 documentation, where you find the paragraph Validation Functions Return Type error.

You can use the standard errors package to check if the error is that, unwrap it, and access the single fields, which are validator.FieldError. From that, you can construct whatever error message you want.

Given an error model like this:

Do I really need to do a request to the server each time the user switches page or refresh page?

That is the safest way. If you want to keep with the current security best practices for SPAs, then using http-only, secure, same-site cookies is the best option. Refreshes won't happen that often on your page, so it shouldn't be a problem.

My initial idea was to use useEffect in the App component where I make a call to the function GetUser() which makes a request to "/get-user" which will user the refreshToken to find the user

What I would do is to first verify the access token, if it's valid then take the userId out of the access token (if you don't have it there you can easily add it as you're creating the tokens manually) and read the user data from the database. If the access token is invalid then return an error to the website and let the user use the refresh token to get a new access token. So I wouldn't mix responsibilities here - I wouldn't use refresh token to get information about the logged in user.

Also I have a question about when I should be calling "/token" in the server to create new access tokens. Should I always try to use the access token to do things that require authentication and if it for example returns null at some point then I make request to "/token" and after that repeat what the user was trying to do?

Yes, that's how it usually is implemented. You make a call with the access token to a protected endpoint. It would be best if the endpoint returned 401 response if the token is expired or invalid. Then your app knows that it should use the refresh token to get a new access token. Once you have a new access token you try to make the call to the protected endpoint again. If you don't manage to get a new access token (e.g. because the refresh token has expired), then you ask the user to log in again.

you can try whereHas mixing with hasOne , to build a new relation: