Skip to content

Conversation

@viktorsmari
Copy link
Collaborator

@viktorsmari viktorsmari commented Aug 21, 2021

Issue #584 has a todo list on what needs to be done for this PR.

This PR is an example on how to start the upgrade to Rails 6 (tests are still failing due to rocket_pants removal)

viktorsmari and others added 8 commits June 11, 2025 00:10
By default we require all Rails frameworks but, 
when ActiveStorage got added, but we do not use.
Best to just disable so not conflig or useless 
configs/migrations.
In future rails app:update is required to add new frameworks manually.
This was already removed from the homepage,
so we can remove controller logic too.
No reason to use a EOL version, and only used to download packages.
Seems now Rails 6 is more strict with the validate line 
and hardcoded IDs in factory.
Also let us run the tests with the lab refree validation 
to be sure passes, bad habbit to hide during tests code.
Created factories for labs with apprval refrees so
validation passes.
Move simple /0/labs, admin routes,
and oauth me to new route.
Install new api serializer to work with Ruby3.
We can add back slowly what is requested
from these commits.
Also removed protected_attributes as not used.
Should upgrade to Dart Sass and 
the sass-embedded gem.
Removed the Trubowyg text-editor as
was holding back upgrade and was not 
working and used only in Pages.
Also pinned admin gem and removed
twitter, deprecated and not used.
Not sure why we have hardcoded test UA header,
needs to be changed with each gem update.
When building the jobs search form, ransack 
needs the relations white listed.
# Conflicts:
#    Gemfile.lock
#    app/views/application/_header.html.haml
#    config/environments/production.rb
#    config/puma.rb
Not sure why this threw exception now, 
but something changed in upgrades.
To give external platforms time to migrate
to new urls, have both domains working.
We can use to know when we can turn 
the old subdomain off.
Not sure why this method was overwritten, 
but caused issue with upgrades. 
To just stick to a RackTest driver and avoid
custom logic, added a simple hidden search 
button so can be clicked by tests. 
Also good for accessibility.
Seems the recent capybara upgrade broke 
the lab create test in relation to multi-select
referee selection and the validation.
Seems RakeTest does not submit data in
expected way.
Maybe with future rails upgrades this 
will be fixed.
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