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

Add a metadata var for public URL to task's public resources' access #1022

Open
ogoletti opened this issue Sep 10, 2024 · 0 comments
Open

Add a metadata var for public URL to task's public resources' access #1022

ogoletti opened this issue Sep 10, 2024 · 0 comments
Labels
Feature request Triage needed Project maintainers still have to review this issue

Comments

@ogoletti
Copy link
Member

Is your feature request related to a problem? Please describe.
When proposing a public resource through a task, one needs to hardcode both the course_id and task_id in the link as documented: https://docs.inginious.org/en/latest/teacher_doc/share_files.html
This is error prone when copy/pasting/duplicating/reusing tasks from one course/year to another.
If the old course/task is still online it might even lead to unexpected behaviors if the new task uses some resources publicly available from the old one.

Describe the solution you'd like
The easiest would be to have a var available that handles the public url (like @publi_url) or something similar that would be agnostic of how the link is created. An public URL could look like:
base_url = @public_url + 'ressource_filename'

Describe alternatives you've considered
A second choice would be to have two vars @course_id and @task_id provided to be able to handle URLs such as:
base_url = '/course/' + @course_id + '/' + @task_id + '/ressource_filename'

@ogoletti ogoletti added Feature request Triage needed Project maintainers still have to review this issue labels Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request Triage needed Project maintainers still have to review this issue
Projects
None yet
Development

No branches or pull requests

1 participant