Nitin's Teams's Features/Plans #37

nitinsandiego · 2024-11-22T03:44:36Z

My Feature

Get Student Details Feature

It takes the student's name and returns all their Github details, allowing Mr. Mortenson and others to quickly and seamlessly check the analytics of specific students.

Backend Work

Gets the details, which contain the GitHub username, of one specific student

@RestController
@RequestMapping("/api/students")
public class StudentApiController {
    @Getter
    public static class CriteriaDto {
        private String name;
        private String course;
        private int trimester;
        private int period; 
    }

    @PostMapping("/find")
    public ResponseEntity<Student> getStudentByCriteria(
            @RequestBody CriteriaDto criteriaDto) {
        
        List<Student> students = studentJPARepository.findByNameCourseTrimesterPeriod(criteriaDto.getName(), criteriaDto.getCourse(), criteriaDto.getTrimester(), criteriaDto.getPeriod());
        
        if (students.isEmpty()) {
            return ResponseEntity.notFound().build();
        } else {
            return ResponseEntity.ok(students.get(0));
        }
    }
}

JPA that connects to SQL database to person query

public interface StudentJPARepository extends JpaRepository<Student, Long> {
    @Query(
        value = "SELECT * FROM students WHERE name = :name AND course = :course AND trimester = :trimester AND period = :period",
        nativeQuery = true
    )
    List<Student> findByNameCourseTrimesterPeriod(
        @Param("name") String name, 
        @Param("course") String course, 
        @Param("trimester") int trimester, 
        @Param("period") int period
    );
}

Frontend Work

One section in the homepage page contains input box

<body>
  <!-- Search Bar -->
  <div class="search-container">
    <input type="text" id="searchName" placeholder="Enter student name">
    <button onclick="searchStudent()">Search</button>
  </div>
<script>
    function searchStudent() {
      const name = document.getElementById("searchName").value;

      const criteriaDto = {
        name: name,
        course: "CSA",
        trimester: 1,
        period: 3
      };

      fetch("http://localhost:8181/api/students/find", {
        method: "POST",
        headers: {
          "Content-Type": "application/json"
        },
        body: JSON.stringify(criteriaDto)
      })
      .then(response => {
        if (!response.ok) {
          throw new Error("Network response was not ok");
        }
        return response.json();
      })
      .then(data => {
        const params = new URLSearchParams({
          name: data.name,
          course: data.course,
          trimester: data.trimester,
          period: data.period
        });
        window.location.href = "/student_2025/student-info?" + params.toString();
      })
      .catch(error => {
        console.error("There was a problem with the fetch operation:", error);
        alert("Student not found.");
      });
    }
  </script>
</body>

Page to display student details

<body>

<div id="details-container">
  <img id="profile-pic" src="" alt="Profile Picture">
  <div class="details-content">
    <p><strong>Username:</strong> <span id="githubUsername"></span></p>
    <p><strong>Profile URL:</strong> <a id="githubProfile" href="" target="_blank"></a></p>
    <p><strong>Issues:</strong> <span id="githubIssues"></span></p>
    <p><strong>Pull Requests:</strong> <span id="githubPulls"></span></p>
    <p><strong>Commits:</strong> <span id="githubCommits"></span></p>
    <p><strong>Public Repos:</strong> <span id="githubRepos"></span></p>
    <p><strong>Public Gists:</strong> <span id="githubGists"></span></p>
    <p><strong>Followers:</strong> <span id="githubFollowers"></span></p>
  </div>
</div>

<script>
  async function fetchStudentDetails() {
    const urlParams = new URLSearchParams(window.location.search);
    const name = urlParams.get("name");
    const course = urlParams.get("course");
    const trimester = urlParams.get("trimester");
    const period = urlParams.get("period");

    const criteriaDto = {
      name: name,
      course: course,
      trimester: parseInt(trimester),
      period: parseInt(period)
    };

    try {
      // Fetch student data from your backend
      const studentResponse = await fetch("http://localhost:8181/api/students/find", {
        method: "POST",
        headers: { "Content-Type": "application/json" },
        body: JSON.stringify(criteriaDto)
      });

      if (!studentResponse.ok) throw new Error("Student not found");

      const student = await studentResponse.json();
      const githubUsername = student.username;

      // Fetch GitHub user profile
      const githubResponse = await fetch(`https://api.github.com/users/${githubUsername}`);
      if (!githubResponse.ok) throw new Error("GitHub profile not found");
      const githubData = await githubResponse.json();

      // Fetch GitHub user events for issues, PRs, and commits data
      const eventsResponse = await fetch(`https://api.github.com/users/${githubUsername}/events`);
      if (!eventsResponse.ok) throw new Error("GitHub events not found");
      const eventsData = await eventsResponse.json();

      // Define the start date for filtering events
      const startDate = new Date("2024-08-01T00:00:00Z");

      // Count events occurring after the start date
      const commitsCount = eventsData.filter(event => 
        event.type === "PushEvent" && new Date(event.created_at) >= startDate
      ).length;

      const prsCount = eventsData.filter(event => 
        event.type === "PullRequestEvent" && new Date(event.created_at) >= startDate
      ).length;

      const issuesCount = eventsData.filter(event => 
        event.type === "IssuesEvent" && new Date(event.created_at) >= startDate
      ).length;

      // Populate the details on the page
      document.getElementById("profile-pic").src = githubData.avatar_url;
      document.getElementById("githubUsername").innerText = githubData.login;
      document.getElementById("githubProfile").href = githubData.html_url;
      document.getElementById("githubProfile").innerText = githubData.html_url;
      document.getElementById("githubRepos").innerText = githubData.public_repos;
      document.getElementById("githubGists").innerText = githubData.public_gists;
      document.getElementById("githubFollowers").innerText = githubData.followers;

      // Display the filtered event data
      document.getElementById("githubIssues").innerText = issuesCount;
      document.getElementById("githubPulls").innerText = prsCount;
      document.getElementById("githubCommits").innerText = commitsCount;

    } catch (error) {
      console.error("Error:", error);
      alert(error.message);
    }
  }

  window.onload = fetchStudentDetails;
</script>

</body>

UML Design

Field Name	Data Type	Description
`id`	`Long`	Unique identifier for each student.
`name`	`String`	Full name of the student.
`username`	`String`	Unique username for the student.
`tableNumber`	`int`	Assigned table number in the classroom.
`course`	`String`	The course the student is enrolled in (e.g., CSSE, CSP, CSA).
`tasks`	`ArrayList<String>`	List of tasks or assignments assigned to the student.
`trimester`	`int`	Trimester during which the student is enrolled.
`period`	`int`	Class period for the student.

What needs to be done

I have files both in the frontend and in the backend. I must first combine this all with my teammates' code into a combined backend and frontend. I then must put all this code onto our branch of the CSA-Coders-2025 backend and frontend. From there, I can then make a pull request to be accepted onto the main CSA 2025 repository. Regarding my collaboration with other teams, specifically CSA Synergy and AI grader, we must make a feature to assign grades to a table. We must also use Person class rather than hardcoding students and only retrieve students using the role ROLE_STUDENT.

The text was updated successfully, but these errors were encountered:

SrinivasNampalli · 2024-11-22T16:40:27Z

The first feature, /update-tasks, allows adding new tasks to a student's existing task list based on their username. If the student is found, the tasks provided in the request are added to their list and saved in the database. If the student is not found, a 404 error is returned.

The second feature, /complete-task, enables marking a specific task as completed. If the student and task exist, the task is removed from the active task list, added to a "completed" list with a "Completed" tag, and saved in the database. If the student or task is not found, an error message is returned.

@Getter
public static class StudentDto {
private String username;
private ArrayList tasks;
}

@PostMapping("/update-tasks")
public ResponseEntity<Student> updateTasks(@RequestBody StudentDto studentDto) {
    String username =  studentDto.getUsername();
    ArrayList<String> tasks = studentDto.getTasks();


    Optional<Student> student = studentJPARepository.findByUsername(username);

    if (student.isPresent()) {
        Student student1 = student.get();
        ArrayList<String> newTasks = student1.getTasks();
        
        for (String task: tasks) {
            newTasks.add(task);
        }
        
        student1.setTasks(newTasks);
        studentJPARepository.save(student1);
        return ResponseEntity.ok(student1);
    }

    return new ResponseEntity<>(HttpStatus.NOT_FOUND);

}
@Getter
public static class TasksDto {
private String username;
private String task;
}

@PostMapping("/complete-task")
public ResponseEntity completeTask(@RequestBody TasksDto tasksDto) {
Optional optionalStudent = studentJPARepository.findByUsername(tasksDto.getUsername());
String task = tasksDto.getTask();

if (optionalStudent.isPresent()) {
    Student student = optionalStudent.get();
    if (student.getCompleted() == null) {
        student.setCompleted(new ArrayList<>()); 
    }

    if (student.getTasks().contains(task)) {
        student.getTasks().remove(task);
        student.getCompleted().add(task + " - Completed");
        studentJPARepository.save(student);
        return ResponseEntity.ok("Task marked as completed.");
    } else {
        return ResponseEntity.badRequest().body("Task not found in the student's task list.");
    }
} else {
    return ResponseEntity.status(404).body("Student not found.");
}

}

Integration for our code:

My plan:

Me and my previous table group partner, Nitin seem to have a general same features. Nitin has already since last tri moved most of the API file where all my code is.

Issues, currently working on fixing up a possible progress bar feature after receiving feedback on Night of the Museum.

Overall the integration process is simple since we only have 3 files and a minor change in the model init file.

Open the right git pull request, after commited code to our main branch combined for this trimester and then from there it will be pushed into our respective repo.

AidanLau10 · 2024-12-03T17:11:03Z

Evaluation of Nitin

Details all the frontend and backend work done and the code. Also has a UML diagram of the attributes of their "Student" which will need to be integrated into the Person table. Steps to be taken details the process of combining his code with his teammates and then making a pull request.

I like how Nitin made it clear what he has done and the steps he will take in the future

Score: 1/1

nitinsandiego added this to CSA Trimester 2 - Integration Planning Nov 22, 2024

nitinsandiego mentioned this issue Nov 22, 2024

Before Turkey CSA P1 and P3 integrations status nighthawkcoders/portfolio_2025#590

Open

nitinsandiego moved this to In review in CSA Trimester 2 - Integration Planning Nov 22, 2024

nitinsandiego changed the title ~~Nitin's Features/Plans~~ Nitin's Teams's Features/Plans Nov 22, 2024

SrijDude3416 added the Mort Toolkit label Nov 25, 2024

aaguy-hue moved this from In review to Done in CSA Trimester 2 - Integration Planning Jan 15, 2025

aaguy-hue closed this as completed by moving to Done in CSA Trimester 2 - Integration Planning Jan 15, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Nitin's Teams's Features/Plans #37

Nitin's Teams's Features/Plans #37

nitinsandiego commented Nov 22, 2024 •

edited

Loading

SrinivasNampalli commented Nov 22, 2024

AidanLau10 commented Dec 3, 2024 •

edited

Loading

Nitin's Teams's Features/Plans #37

Nitin's Teams's Features/Plans #37

Comments

nitinsandiego commented Nov 22, 2024 • edited Loading

My Feature

Get Student Details Feature

Backend Work

Frontend Work

UML Design

What needs to be done

SrinivasNampalli commented Nov 22, 2024

AidanLau10 commented Dec 3, 2024 • edited Loading

nitinsandiego commented Nov 22, 2024 •

edited

Loading

AidanLau10 commented Dec 3, 2024 •

edited

Loading