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

Update rails to 7.1.3.4 and replace dotenv-rails with dotenv #80

Merged
merged 3 commits into from
Jun 30, 2024

Conversation

dmitryrck
Copy link
Member

Main things:

Honestly, I am not too happy with the way I fixed the controllers tests. Rails probably changed and it needs now the ENV var at boot. Happy to have someone else trying.

✌️

Copy link
Collaborator

@sarahhay7 sarahhay7 left a comment

Choose a reason for hiding this comment

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

Thanks for going through this @dmitryrck

It all looks good to me. We have previously used the :destroy action on the members controller in a script for culling members who have been inactive for 3+ years, but I think it's right to remove it from the controller. We can add back it in future if needed (or just modify the database directly).

@sarahhay7
Copy link
Collaborator

@dmitryrck I only noticed one controller test being added. Is it possible there are more commits that haven't been included in this PR?

@dmitryrck
Copy link
Member Author

Thanks for going through this @dmitryrck

🙏

[…] We have previously used the :destroy action on the members controller in a script for culling members who have been inactive for 3+ years.

If I recall that correctly it was done using rails console, there is no action destroy in that controller. I removed it from that list because rails started to complain that I don't have an action destroy.

@dmitryrck I only noticed one controller test being added. Is it possible there are more commits that haven't been included in this PR?

Nop. The tests already in the main branch only test the "best case scenario". I added a "wrong case scenario" to make sure the authentication is blocking users with wrong password.

Thanks for the review :)

@sarahhay7
Copy link
Collaborator

@dmitryrck You're totally right 😅 Can't believe that was only 3 years ago 👀
And thanks again 🙌

@parndt parndt merged commit 53ba180 into main Jun 30, 2024
1 check passed
@parndt
Copy link
Member

parndt commented Jun 30, 2024

I'll get this deployed

@parndt parndt deleted the update-gems branch June 30, 2024 23:09
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