Correct formatting for hyperlink about codechat_system

[jpg323]

We formatted the hyperlink successfully. The hyperlink still doesn't navigate anywhere. The link is created in the code at the bottom of Codechat_Client.js and the function definition is in render_manager.py if you search for "navigate_to_error"

[LoganJohnson98]

Project Assignment 1:

Provide a detailed plan that:

Describes the feature you will add.

For this project, we will modify the existing CodeChat code so that it properly hyperlinks the file and the line. During this process, we will document any relevant information such as an explanation on ‘Regular Expressions’ in addition to any changes that we make.

Defines which repository/repositories your code will be added to.

Our documentation and code will be merged into the branch at CodeChat_system.

Specifies what libraries, languages, and interfaces your code must work with.

Our code is primarily going to be written in JavaScript. I think that any edits should continue to work on any operating system that is already running CodeChat.

Details a series of steps you will follow to complete this feature.

The first step in this coding project is understanding how hyperlinks are currently handled in CodeChat.

Defines tests to show the feature works correctly.

The exact formatting is to be determined. We will test the error hyperlinking with multiple different types of errors. Another project requirement is that the hyperlink should bring you to the line as well as highlight the line that contains the error.

Outlines goals for scrum 1 and scrum 2.

Scrum 1 goals:

• Clearly define the project scope
• State the location of all changes
• Track tips and tricks on the way
• Provide clear documentation on functionality on existing hyperlink code
• Provide a list of steps required to complete the project
• Complete as much of the project as possible

Scrum 2 goals:

• Understand the new project scope before attempting to solve the problem
• Track each time we get stuck attempting to edit the project
• Provide clear documentation on any issues or bugs that we are able to solve
• Hopefully: Complete the project!

Completed Thursday March 24, 2023

[jpg323]

Here is some developer documentation we developed throughout the process to help with turnover and future users.