Moderator Tool Improvements #767
Draft
This pull request is big! We’re only showing the most recent 250 commits.
Commits on Feb 16, 2023
-
-
-
-
-
-
-
-
-
-
-
New dependencies require ruby 2.7 and rails 6.0 as minimum versions.
-
It seems that the update to rubocop/rails means we get some new rules. The new rules seem to have changed their minds on how some things should look or be done. This applies the new rules.
-
-
-
-
Check media type rather than content type
Also swap arguments around such that the error message upon failure lists the right value as expected.
-
-
Remove comments of safely updated packages
Also add a note in the INSTALLATION about the ruby versions that are supported/not supported.
-
-
Switch to rails 6 defaults and cleanup safe settings
The only setting left in new_framework_defaults_6.0 is about updating the cookies. If the system runs stable on rails 6, the file can be removed and the upgrade is completed.
-
Fix files without .html extension
Rails 6.1 is more picky about the response formats, and not having the intended html extension can cause issues.
-
-
-
-
-
Upgrade puma and clean up Gemfile
Package notes are added into the PR instead.
-
-
-
Fix flag fixture polymorphic relation without type
When a relation is polymorphic, the type of the target must be specified in the fixture, otherwise the polymorphic_type field is not set and the record is invalid.
-
-
-
Update sass-rails to sassc-rails
Fix invalid SCSS
-
The user is not present on those posts, and rails 6 performs better validations. It must be marked as optional to fix the issue.
-
-
-
The namespaced env cache needs to be recreated after forking. With the old method of changing the Rails cache, this was not happening correctly.
-
The namespaced env cache breaks multiple rubocop rules with regards to using map on a hash-like object. However, the suggested fixes break the intention of the code. Therefore, I have added it to be ignored.
-
-
-
Remove new defaults initializer
Otherwise, new checkouts/installs of the project would not run with recommended settings.
-
-
-
Update sass-rails to sassc-rails
Fix invalid SCSS
-
-
-
-
-
-
-
-
Use less specific versions to prevent image removals from breaking the CI.
-
-
-
-
-
Changed error messages to avoid 'tags can't have more than 5 tags' co…
…nstruct. I realize that usually we want to attach an error to the field (:tags) not the post (:base), but I couldn't come up with wordings that were clear and the error messages point to tags as the problem, so I think this is ok.
-
-
-
-
-
-
In seeding, actually link to the corresponding objects
Previously, we would pass ids to the creation handler. However, this does not pass validations whenever the association is non-optional (i.e. belongs_to). With these changes, we pass the actual Rails objects instead of just the ids, which does pass the validations and sets it properly.
-
-
Revert redis to version 4 until issue is fixed and update settings
Settings are now properly loaded from the database.yml config file, rather than only taking some of those settings.
-
-
Add back still required install instructions
The `rmagick` library requires imagemagick to also be installed (libvips is the new default used by image processing in rails).
-
-
-
Add some notes on docker compose and Mac
Also update display
-
-
-
-
-
-
-
Bump nokogiri from 1.13.8 to 1.13.9
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.13.8 to 1.13.9. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md) - [Commits](sparklemotion/nokogiri@v1.13.8...v1.13.9) --- updated-dependencies: - dependency-name: nokogiri dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
-
Bump commonmarker from 0.23.5 to 0.23.6
Bumps [commonmarker](https://github.com/gjtorikian/commonmarker) from 0.23.5 to 0.23.6. - [Release notes](https://github.com/gjtorikian/commonmarker/releases) - [Changelog](https://github.com/gjtorikian/commonmarker/blob/main/CHANGELOG.md) - [Commits](gjtorikian/commonmarker@v0.23.5...v0.23.6) --- updated-dependencies: - dependency-name: commonmarker dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
-
- Add devise_saml_authenticatable - Add saml_authenticatable to user - Add SamlInit concern + attribute map - Add devise config for SAML - Add site settings for SAML - Add SsoProfile model - Add conditional SAML routes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Bump loofah from 2.18.0 to 2.19.1
Bumps [loofah](https://github.com/flavorjones/loofah) from 2.18.0 to 2.19.1. - [Release notes](https://github.com/flavorjones/loofah/releases) - [Changelog](https://github.com/flavorjones/loofah/blob/main/CHANGELOG.md) - [Commits](flavorjones/loofah@v2.18.0...v2.19.1) --- updated-dependencies: - dependency-name: loofah dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
-
Bump rails-html-sanitizer from 1.4.3 to 1.4.4
Bumps [rails-html-sanitizer](https://github.com/rails/rails-html-sanitizer) from 1.4.3 to 1.4.4. - [Release notes](https://github.com/rails/rails-html-sanitizer/releases) - [Changelog](https://github.com/rails/rails-html-sanitizer/blob/master/CHANGELOG.md) - [Commits](rails/rails-html-sanitizer@v1.4.3...v1.4.4) --- updated-dependencies: - dependency-name: rails-html-sanitizer dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
-
-
-
-
-
Fix tour test for the 3rd time
Also add tests to ensure that the tagset is correctly created by the seeds.
-
-
-
- Fix rubocop errors accidentally merged - Fix failing test
-
-
-
-
-
-
-
-
-
-
-
update Ruby version info (since we've moved to Ruby 3 I don't know if…
… we still support 2.7, so hedging a little there)
-
-
-
-
-
-
-
-
-
Added search results post count and adjusted styling to accommodate
-
Adjusted styling to better conform with project standards.
-
Bump globalid from 1.0.0 to 1.0.1
Bumps [globalid](https://github.com/rails/globalid) from 1.0.0 to 1.0.1. - [Release notes](https://github.com/rails/globalid/releases) - [Commits](rails/globalid@v1.0.0...v1.0.1) --- updated-dependencies: - dependency-name: globalid dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
-
-
-
-
Bump rack from 2.2.4 to 2.2.6.2
Bumps [rack](https://github.com/rack/rack) from 2.2.4 to 2.2.6.2. - [Release notes](https://github.com/rack/rack/releases) - [Changelog](https://github.com/rack/rack/blob/main/CHANGELOG.md) - [Commits](rack/rack@2.2.4...v2.2.6.2) --- updated-dependencies: - dependency-name: rack dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
-
-
-
-
-
-
-
Update app/models/suggested_edit.rb
Co-authored-by: Taico Aerts <[email protected]>
-
-
-
Move check for signed in user from preferences function to preference
Previously the QPixel.preferences function returned null when there was no signed in user. This caused an error as the QPixel.preference function tried to access properties of null. Now the check for a signed in user happens in QPixel.preference and this function returns null when there is no signed in user. The three places that currently use this return value all behave correctly when there is no signed in user - the null does not cause incorrect behaviour.
-
-
-
-
-
Bump commonmarker from 0.23.6 to 0.23.7
Bumps [commonmarker](https://github.com/gjtorikian/commonmarker) from 0.23.6 to 0.23.7. - [Release notes](https://github.com/gjtorikian/commonmarker/releases) - [Changelog](https://github.com/gjtorikian/commonmarker/blob/main/CHANGELOG.md) - [Commits](gjtorikian/commonmarker@v0.23.6...v0.23.7) --- updated-dependencies: - dependency-name: commonmarker dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Commits on Feb 17, 2023
Commits on Jun 25, 2023
Commits on Aug 6, 2023
Commits on Aug 18, 2023
Commits on Aug 29, 2023
Commits on Oct 25, 2023
Commits on Feb 13, 2024
Commits on Mar 9, 2024
Commits on Mar 18, 2024
Commits on May 11, 2024
Commits on May 25, 2024
Commits on May 29, 2024
Commits on Jun 3, 2024
Commits on Jun 7, 2024
Commits on Jun 24, 2024
Commits on Jun 26, 2024
Commits on Jun 27, 2024
Commits on Jun 28, 2024
Commits on Jul 5, 2024
Commits on Jul 8, 2024
Commits on Jul 9, 2024
Commits on Jul 23, 2024
Commits on Aug 29, 2024
Commits on Sep 1, 2024
-
-
-
-
Apply Taeir's suggestion from a comment on pull request 1009
Taeir's explanation: NOTE: I use select here to allow rails to merge the two operations into one query and avoid loading the full ThreadFollower objects
-
-
Commits on Sep 3, 2024
Commits on Sep 5, 2024
Commits on Sep 6, 2024
Commits on Sep 11, 2024
Commits on Sep 12, 2024
Commits on Sep 26, 2024
Commits on Oct 3, 2024
Commits on Oct 7, 2024
Commits on Oct 14, 2024
Commits on Oct 16, 2024
Commits on Oct 20, 2024
Commits on Oct 25, 2024
Commits on Oct 26, 2024
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.