-
Notifications
You must be signed in to change notification settings - Fork 109
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
Support Making Links to The Test Data to Allow Cloning Problems #287
Comments
@iceb0y |
When a user views a cloned problem,he/she should have permission to view problems in both domains. |
@q234rty |
Or: |
??? When (other users) view or submit the cloned problem, regard the cloned problem the same as normal problems. |
Since the link is at the data level, it has no relation with the permission system in Vijos. For simplicity, I'd suggest cloned problems not inherit permissions. Otherwise the web need to implement data parser to recognize links in the data. |
Another aspect to consider is, whether cloned data should keep sync with the source data. Semantically cloned data should keep a "snapshot" of the source data. We need to have a careful design for this feature. |
It is also possible to do this at web level. |
@q234rty The important point is:
|
Maybe cloned problems don't need data files. |
Well, using data can make changes easily and avoid no data warnings without any changes. |
The current data file is a legacy format. We don't want to add new features to it. We have proposed a new data format but don't have enough motivation to do it. |
Just change the Config.ini, set the first line to a non-positive number such as -1, and the second line is the problem id in main-site. When judging the problem, treat it as submitted a solution in main site.
So, this solution has these advantages:
New featureThe text was updated successfully, but these errors were encountered: