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

Fix legacy 'exercises' path support #5854

Merged
merged 1 commit into from
Oct 10, 2024
Merged

Conversation

jorg-vr
Copy link
Contributor

@jorg-vr jorg-vr commented Oct 10, 2024

This pull request fixes the support for the path /courses/?/series/?/exercises/?/submissions.

The /exercises paths have all been renamed to /activities, yet our routes still offer legacy support for /exercises. I didn't find any internal references that use the /exercises name, so I assume the bug was discovered by an external link.

I am also open to dropping the support for /exercises

  • test were added

Fixes an issue come in by mail, where a user tried to navigate to https://dodona.be/en/courses/156/series/2328/exercises/1963184607/submissions
For reference, the internally linked path https://dodona.be/en/courses/156/series/2328/activities/1963184607/submissions does work

@jorg-vr jorg-vr added the bug Something isn't working label Oct 10, 2024
@jorg-vr jorg-vr self-assigned this Oct 10, 2024
Copy link

coderabbitai bot commented Oct 10, 2024

Walkthrough

The changes involve updates to the SubmissionsController in the app/controllers/submissions_controller.rb, specifically in the set_submissions method. This method now checks for both params[:activity_id] and params[:exercise_id], allowing for more flexible handling of submissions. Additionally, comments have been updated to reflect valid routes. In the test suite, a new test case has been added to SubmissionsControllerTest to validate access to legacy paths that include exercise.

Changes

File Change Summary
app/controllers/submissions_controller.rb Updated set_submissions method to check both params[:activity_id] and params[:exercise_id]. Comments updated for route clarity.
test/controllers/submissions_controller_test.rb Added new test method test 'should be able to use legacy paths containing exercise' to verify access to legacy paths.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant SubmissionsController
    participant ExerciseModel

    User->>SubmissionsController: GET /activities/:id/submissions or /exercises/:id/submissions
    SubmissionsController->>SubmissionsController: set_submissions(params)
    SubmissionsController->>ExerciseModel: Find Exercise by activity_id or exercise_id
    ExerciseModel-->>SubmissionsController: Return Exercise object
    SubmissionsController-->>User: Render submissions
Loading

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)
app/controllers/submissions_controller.rb (1)

178-180: LGTM! Consider future-proofing the comment.

The changes effectively address the PR objective of fixing legacy 'exercises' path support. The new logic allows for backward compatibility while maintaining existing functionality.

Consider updating the comment to indicate that the '/exercises' path is for legacy support:

- # both /activities/:id/submissions and /exercises/:id/submissions are valid routes
+ # /activities/:id/submissions is the primary route, /exercises/:id/submissions is supported for legacy compatibility

This change would make it clearer that '/exercises' is a legacy path, which aligns better with the possibility of removing it in the future, as mentioned in the PR objectives.

test/controllers/submissions_controller_test.rb (1)

464-469: LGTM! Consider enhancing the test for explicit path verification.

The test case effectively checks the accessibility of the legacy path containing 'exercise'. It aligns well with the PR objective of fixing legacy 'exercises' path support.

To make the test more robust, consider adding an explicit check to verify that the generated path contains 'exercise' instead of 'activity'. This can be done by asserting on the generated path before making the request. Here's a suggested enhancement:

 test 'should be able to use legacy paths containing `exercise`' do
   course = create :course, series_count: 1, activities_per_series: 1
+  path = course_series_exercise_submissions_path(course, course.series.first, course.series.first.exercises.first)
+  assert_includes path, 'exercise', "Generated path should contain 'exercise'"
-  get course_series_exercise_submissions_path(course, course.series.first, course.series.first.exercises.first)
+  get path

   assert_response :ok
 end

This addition ensures that the test explicitly verifies the presence of 'exercise' in the generated path, making the test more comprehensive.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 6764da6 and 073cdeb.

📒 Files selected for processing (2)
  • app/controllers/submissions_controller.rb (1 hunks)
  • test/controllers/submissions_controller_test.rb (1 hunks)
🧰 Additional context used
🔇 Additional comments (2)
app/controllers/submissions_controller.rb (1)

178-180: Verify test coverage for the changes.

The changes look good and address the PR objectives. However, it's important to ensure that appropriate tests have been added to cover this new functionality.

Could you please confirm that tests have been added to verify:

  1. The legacy '/exercises' path works as expected.
  2. The existing '/activities' path continues to function correctly.
  3. Both activity_id and exercise_id parameters are handled properly in various scenarios.

If these tests are in a separate file, please provide a link to the test file for review.

test/controllers/submissions_controller_test.rb (1)

Line range hint 1-469: Overall, the changes look good and align with the PR objectives.

The addition of the new test case for legacy path support is appropriate and well-implemented. It effectively addresses the PR's main goal of fixing support for the legacy 'exercises' path.

The rest of the test suite remains unchanged and appears to provide comprehensive coverage for various aspects of submission handling, which is commendable.

Copy link
Member

@bmesuere bmesuere left a comment

Choose a reason for hiding this comment

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

Since exercises is supported in our routes, we should handle it properly in the controllers. 👍

@jorg-vr jorg-vr merged commit 248fe9d into main Oct 10, 2024
15 of 16 checks passed
@jorg-vr jorg-vr deleted the fix/exercise-path-support branch October 10, 2024 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants