Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Obsolete
-
Affects Version/s: Current Version
-
Fix Version/s: Far Future
-
Component/s: OIOIOI
-
Labels:
Description
And this everything just to show scores in submissions diff view...
Current design doesn't cooperate well with cross-users submission privileges. Sometimes (namely in cheaters app, source publicizing) we want to show source code (and score in the latter) to non-owner and non-admin, but reusing existing views (especially for source) breaks, when other part of the code want's to show there some useful info.
What we have thought so far:
* It would be really great, to not have to worry in templates whether we should add some diff to check is value is visible. We can achieve that by creating wrapper over Submission objects, which sets to None inaccessible attributes.
* (already forgot)
Current design doesn't cooperate well with cross-users submission privileges. Sometimes (namely in cheaters app, source publicizing) we want to show source code (and score in the latter) to non-owner and non-admin, but reusing existing views (especially for source) breaks, when other part of the code want's to show there some useful info.
What we have thought so far:
* It would be really great, to not have to worry in templates whether we should add some diff to check is value is visible. We can achieve that by creating wrapper over Submission objects, which sets to None inaccessible attributes.
* (already forgot)
Activity
- All
- Comments
- History
- Activity
- Transitions
- Commits
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.
Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.
