Skip to content

Conversation

@Girik1105
Copy link
Contributor

@Girik1105 Girik1105 commented Oct 30, 2025

Guidelines for Pull Requests

If you haven't yet read our code review guidelines, please do so, You can find them here.

Please confirm the following by adding an x for each item (turn [ ] into [x]).

  • I have removed all code style changes that are not necessary (e.g. changing blanks across the whole file that don’t need to be changed, adding empty lines in parts other than your own code)
  • I am not making any changes to files that don’t have any effect (e.g. imports added that don’t need to be added)
  • I do not have any sysout statements in my code or commented out code that isn’t needed anymore
  • I am not reformatting any files in the wrong format or without cause.
  • I am not changing file encoding or line endings to something else than UTF-8, LF
  • My pull request does not show an insane amount of files being changed although my ticket only requires a few files being changed
  • I have added Javadoc/documentation where appropriate
  • I have added test cases where appropriate
  • I have explained any part of my code/implementation decisions that is not be self-explanatory

Please provide a brief description of your ticket

(you can copy the ticket if it hasn't changed)

Add Bibliography section to staff page

Like users or images, it should show all references sortable by author, year, title, or created date.

VSPC-150

Anything else the reviewer needs to know?

The previous PR for this branch 299 has a force push and hence cannot be re opened.

pradeep-017 and others added 30 commits May 5, 2021 16:28
… them, fixed code indentations and div alignments
…aphy, handling null cases of path variables, code cleanup
…ged Biblio controller and forms - Saving is working - Work in Progress
Copy link
Member

@jdamerow jdamerow left a comment

Choose a reason for hiding this comment

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

Also, there are codefactor issues and what happened to all the classes in the "references" package (e.g. https://github.com/diging/virtual-spaces-2.0/pull/299/files#diff-8e2f9f515ef07dfc360ae67df0401001f8cd6b89b960b99068f972b3fd962eec)

reference.setEditors(editor);
reference.setType(type);
reference.setNote(note);
if(visibility == "Private") {
Copy link
Member

Choose a reason for hiding this comment

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

strings should not be hard-coded; at a minimum this needs to be a constant somewhere


private String note;

private boolean visibility;
Copy link
Member

Choose a reason for hiding this comment

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

boolean variables should be adjectives so that the methods make sense when you call them is... (i.e. isVisibility does not make much sense...)

@jdamerow jdamerow closed this Oct 30, 2025
@Girik1105 Girik1105 reopened this Nov 6, 2025
@jdamerow
Copy link
Member

jdamerow commented Nov 7, 2025

Make it so, Jenkins.

@RequestMapping(value = "/staff/module/{id}/slide/{slideId}/bibliography/{biblioId}/reference/add",
method = RequestMethod.POST)
public ResponseEntity<IReference> addReference(@PathVariable("id") String moduleId,
public ResponseEntity<Reference> addReference(@PathVariable("id") String moduleId,
Copy link
Member

Choose a reason for hiding this comment

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

is this needed? why the change?

@jdamerow
Copy link
Member

jdamerow commented Nov 7, 2025

  • when sorting the table, the column widths change, which they shouldn't
  • there should be a column that has the module a reference belongs to and a link that gets you to the slide that has the reference

@jdamerow jdamerow closed this Nov 7, 2025
@Girik1105 Girik1105 reopened this Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants