tw4 / log-monitoring-tools Goto Github PK

Describe the bug
"I can add multiple paths with the same name."

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
I cannot add multiple paths with the same name.

Screenshots
If applicable, add screenshots to help explain your problem.

Screen.Recording.2024-06-20.at.12.04.16.mov

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Summary

The application currently supports only Windows and macOS ARM-based versions. However, we would like to request support for standard Windows 11 and 10 versions as well.

Rationale

Many users are still using non-ARM-based versions of Windows 11 and 10. These users are unable to use the application, thus limiting its reach. Supporting standard Windows versions will make the application accessible to a broader audience.

Expected Behavior

The application should work seamlessly on non-ARM-based Windows 11 and 10 versions.

Steps

1. Conduct compatibility tests for the application on standard Windows 11 and 10 versions.
2. Implement necessary adjustments and optimizations.
3. Release the updated version and notify users.

Additional Information

• Compatibility documentation for Windows 11 and 10 versions can be accessed.
• Beta testers can be engaged to gather feedback if necessary.

Thank you.

Is your feature request related to a problem? Please describe.
I'm always frustrated when I need to download specific log files from the log detay sekmesi but there is no option to do so. This forces me to manually copy and save the logs, which is time-consuming and prone to errors.

Describe the solution you'd like
I would like to have a feature that allows users to download log files directly from the log detay sekmesi. This would streamline the process, making it faster and more efficient to obtain the necessary log files for analysis or record-keeping.

Describe alternatives you've considered

1. Copy to Clipboard: Adding a button to copy the entire log content to the clipboard, which users can then paste into a text file manually.
2. Export to Email: An option to email the log file directly from the log detay sekmesi to the user or other stakeholders.
3. Cloud Storage Integration: Integrating with cloud storage services like Google Drive or Dropbox to save logs directly to these platforms.

Additional context
This feature would be especially useful for teams that need to frequently share log files for troubleshooting or auditing purposes. The ability to download logs directly from the log detay sekmesi would enhance productivity and reduce the risk of manual errors.

Screenshots or mock-ups of the proposed download button and its placement within the log detay sekmesi would help in visualizing the implementation and discussing further details.

Summary

Create unit tests for the File.tsx component to ensure it functions as expected.

Background

The File.tsx component is used to represent individual files within the application. It is important to verify that it displays file information correctly and handles interactions properly.

Expected Behavior

The File.tsx component should render file information accurately and respond to user interactions as expected.

Steps to Reproduce

Provide a step-by-step guide on how to test the component manually.

1. Navigate to the file list.
2. Verify the rendering of individual files.
3. Interact with the file component (e.g., click, hover).

Test Cases

List specific test cases that need to be verified.

• Test case 1: Ensure the component renders file information correctly.
• Test case 2: Verify that user interactions are handled properly.
• Test case 3: Check that the component updates correctly based on props changes.

Additional Information

Include any additional information, screenshots, or logs that could help the tester. Provide links to relevant documentation or related issues if available.

Environment

Specify the environment in which the testing should be conducted.

• Operating System: (e.g., Windows 10, macOS Catalina, Ubuntu 20.04)
• Browser: (if applicable, e.g., Chrome, Firefox)
• Other relevant details: (e.g., specific hardware, configurations)

Checklist

• Test cases have been clearly defined.
• All necessary information for reproducing the issue or testing the feature has been provided.
• Expected behavior is well described.

Thank you for conducting this testing!

Summary

Create unit tests for the Home.tsx component to ensure it functions as expected.

Background

The Home.tsx component is a key part of the application, displaying the home page. It needs to be thoroughly tested to verify that it renders correctly and interacts with other components as intended.

Expected Behavior

The Home.tsx component should render the correct content based on the application's state. It should handle user interactions properly and update the UI as expected.

Steps to Reproduce

Provide a step-by-step guide on how to test the component manually.

1. Navigate to the home page.
2. Verify the initial render of the Home.tsx component.
3. Interact with the component and verify UI updates.

Test Cases

List specific test cases that need to be verified.

• Test case 1: Ensure the component renders correctly.
• Test case 2: Verify that state changes are handled properly.
• Test case 3: Check that user interactions are processed correctly.

Additional Information

Include any additional information, screenshots, or logs that could help the tester. Provide links to relevant documentation or related issues if available.

Environment

Specify the environment in which the testing should be conducted.

• Operating System: (e.g., Windows 10, macOS Catalina, Ubuntu 20.04)
• Browser: (if applicable, e.g., Chrome, Firefox)
• Other relevant details: (e.g., specific hardware, configurations)

Checklist

• Test cases have been clearly defined.
• All necessary information for reproducing the issue or testing the feature has been provided.
• Expected behavior is well described.

Thank you for conducting this testing!

Is your feature request related to a problem? Please describe.
I'm always frustrated when I need to find specific types of files in the File List because there is no option to filter files by their extension.

Describe the solution you'd like
I would like to have a feature in the File List that allows users to filter files based on their extension. This would make it easier to locate specific files quickly.

Describe alternatives you've considered
An alternative solution could be a search bar where users can input the file extension they are looking for, and it will only display the files matching that extension.

Additional context
Here is a screenshot of the current File List for reference:

This feature would greatly enhance the user experience by simplifying the process of finding specific files among many.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
When I add a new path, I can quickly see it on the path list.

Screenshots
https://github.com/tw4/log-monitoring-tools/assets/88425310/e6282873-beff-49ad-9fe6-5894ee814ba2

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Summary

After listing the files in a path, users should be able to refresh the page using a button.

Rationale

Currently, users have to manually refresh the page to update the file list, which can negatively impact the user experience. Adding a refresh button will allow users to update the file list more easily and quickly.

Expected Behavior

After listing the files in the path, pressing a button should refresh the page and update the file list.

Steps

1. Review the existing function that lists files in the path.
2. Add a refresh button and link it to the necessary functions.
3. Test the refresh button to ensure it works correctly.

Additional Information

• It is important for the refresh button to be placed in a visible location to facilitate easy access for users.
• User feedback can be collected to make further improvements if necessary.

Thank you.

Summary

Create unit tests for the LogContent.tsx component to ensure it functions as expected.

Background

The LogContent.tsx component is responsible for displaying log content within the application. It's essential to verify that it renders log entries accurately and handles interactions properly.

Expected Behavior

The LogContent.tsx component should render log entries accurately and handle interactions such as scrolling and selecting log entries.

Steps to Reproduce

Provide a step-by-step guide on how to test the component manually.

1. Navigate to the page where log content is displayed.
2. Verify the rendering of log entries.
3. Interact with the log content (e.g., scroll, select log entries).

Test Cases

List specific test cases that need to be verified.

• Test case 1: Ensure the component renders log entries correctly.
• Test case 2: Verify that log entries are displayed dynamically.
• Test case 3: Check that interactions with the log content (e.g., scrolling, selection) are handled properly.

Additional Information

Include any additional information, screenshots, or logs that could help the tester. Provide links to relevant documentation or related issues if available.

Environment

Specify the environment in which the testing should be conducted.

• Operating System: (e.g., Windows 10, macOS Catalina, Ubuntu 20.04)
• Browser: (if applicable, e.g., Chrome, Firefox)
• Other relevant details: (e.g., specific hardware, configurations)

Checklist

• Test cases have been clearly defined.
• All necessary information for reproducing the issue or testing the feature has been provided.
• Expected behavior is well described.

Thank you for conducting this testing!

Summary

Create unit tests for the Log.tsx component to ensure it functions as expected.

Background

The Log.tsx component is responsible for displaying logs within the application. It needs thorough testing to ensure it displays the log entries correctly and updates as new logs are added.

Expected Behavior

The Log.tsx component should display log entries accurately and handle updates dynamically. It should also handle any errors gracefully.

Steps to Reproduce

Provide a step-by-step guide on how to test the component manually.

1. Navigate to the log page.
2. Verify the initial render of the Log.tsx component.
3. Add new log entries and verify they appear correctly.

Test Cases

List specific test cases that need to be verified.

• Test case 1: Ensure the component renders the log entries correctly.
• Test case 2: Verify that new log entries are displayed dynamically.
• Test case 3: Check that errors are handled gracefully.

Additional Information

Include any additional information, screenshots, or logs that could help the tester. Provide links to relevant documentation or related issues if available.

Environment

Specify the environment in which the testing should be conducted.

• Operating System: (e.g., Windows 10, macOS Catalina, Ubuntu 20.04)
• Browser: (if applicable, e.g., Chrome, Firefox)
• Other relevant details: (e.g., specific hardware, configurations)

Checklist

• Test cases have been clearly defined.
• All necessary information for reproducing the issue or testing the feature has been provided.
• Expected behavior is well described.

Thank you for conducting this testing!

Summary

Create unit tests for the FileList.tsx component to ensure it functions as expected.

Background

The FileList.tsx component is responsible for displaying a list of files within the application. Proper testing is required to ensure that it renders the list correctly and handles updates and interactions properly.

Expected Behavior

The FileList.tsx component should render a list of files accurately and update the list based on interactions and changes in the file data.

Steps to Reproduce

Provide a step-by-step guide on how to test the component manually.

1. Navigate to the page where the file list is displayed.
2. Verify the rendering of the file list.
3. Interact with the file list (e.g., scroll, click on files).

Test Cases

List specific test cases that need to be verified.

• Test case 1: Ensure the component renders the file list correctly.
• Test case 2: Verify that the file list updates dynamically when new files are added or removed.
• Test case 3: Check that interactions with the file list (e.g., clicking on files) are handled properly.

Additional Information

Include any additional information, screenshots, or logs that could help the tester. Provide links to relevant documentation or related issues if available.

Environment

Specify the environment in which the testing should be conducted.

• Operating System: (e.g., Windows 10, macOS Catalina, Ubuntu 20.04)
• Browser: (if applicable, e.g., Chrome, Firefox)
• Other relevant details: (e.g., specific hardware, configurations)

Checklist

• Test cases have been clearly defined.
• All necessary information for reproducing the issue or testing the feature has been provided.
• Expected behavior is well described.

Thank you for conducting this testing!

Summary

The component displaying files should include syntax highlighting for different programming languages (e.g., C++ or Python).

Rationale

To enhance the readability and clarity of code files, syntax highlighting specific to the programming languages in question should be implemented. This will enable developers to review code more quickly and accurately.

Expected Behavior

The component displaying files should apply syntax highlighting for keywords and syntax specific to programming languages like C++ and Python.

Steps

1. Review the existing component that displays code files.
2. Research and integrate syntax highlighting libraries into the project.
3. Add customized color schemes for different programming languages.
4. Test the syntax highlighting to ensure it functions correctly.

Additional Information

• Popular syntax highlighting libraries (e.g., Prism, Highlight.js) can be used.
• User feedback can be collected to further improve the color schemes.

Thank you.

Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to sift through a long list of log paths in the loglist. It takes a lot of time and effort to find the specific logs I need, which reduces productivity and makes log analysis cumbersome.

Describe the solution you'd like
I would like to have a filtering feature that allows me to select specific paths from the loglist. This way, I can quickly narrow down the list to only the relevant logs I need to review, making the process much more efficient and user-friendly.

Describe alternatives you've considered

1. Search Functionality: Implementing a search bar that allows users to type in keywords or parts of the path to quickly locate logs.
2. Tagging System: Allowing users to tag logs with keywords or categories, and then filter based on these tags.
3. Sorting Options: Providing various sorting options (e.g., alphabetically, by date added) to help users manage and locate logs more easily.

Additional context
This feature would be particularly useful in environments with a high volume of log data, where users need to regularly access and analyze logs from different sources. A filtering option based on paths would greatly enhance usability and efficiency.

Screenshots or mock-ups of how this feature could be integrated into the current UI would be beneficial for further understanding and discussion.

Summary

Create unit tests for the MainLayout.tsx component to ensure it functions as expected.

Background

The MainLayout.tsx component is a crucial part of the application's layout structure. It's important to verify that it renders child components correctly and handles layout changes appropriately.

Expected Behavior

The MainLayout.tsx component should render child components accurately and respond to changes in layout (e.g., screen resizing) gracefully.

Steps to Reproduce

Provide a step-by-step guide on how to test the component manually.

1. Navigate to a page where the MainLayout.tsx component is used.
2. Verify the rendering of child components within the layout.
3. Test layout changes (e.g., resizing the browser window).

Test Cases

List specific test cases that need to be verified.

• Test case 1: Ensure the component renders child components correctly.
• Test case 2: Verify that the layout adjusts properly to changes in screen size.
• Test case 3: Check that child components are positioned correctly within the layout.

Additional Information

Include any additional information, screenshots, or logs that could help the tester. Provide links to relevant documentation or related issues if available.

Environment

Specify the environment in which the testing should be conducted.

• Operating System: (e.g., Windows 10, macOS Catalina, Ubuntu 20.04)
• Browser: (if applicable, e.g., Chrome, Firefox)
• Other relevant details: (e.g., specific hardware, configurations)

Checklist

• Test cases have been clearly defined.
• All necessary information for reproducing the issue or testing the feature has been provided.
• Expected behavior is well described.

Thank you for conducting this testing!

Summary

Create unit tests for the AddNewPath.tsx component to ensure it functions as expected.

Background

The AddNewPath.tsx component is part of the settings section, allowing users to add new paths. It is crucial to ensure that this component works correctly to prevent issues with path management.

Expected Behavior

The AddNewPath.tsx component should allow users to input new paths and save them correctly. It should validate the input and provide appropriate feedback.

Steps to Reproduce

Provide a step-by-step guide on how to test the component manually.

1. Navigate to the settings page.
2. Open the AddNewPath.tsx component.
3. Enter a new path and save it.

Test Cases

List specific test cases that need to be verified.

• Test case 1: Ensure the component renders correctly.
• Test case 2: Verify that the input is validated properly.
• Test case 3: Check that new paths are saved correctly.

Additional Information

Include any additional information, screenshots, or logs that could help the tester. Provide links to relevant documentation or related issues if available.

Environment

Specify the environment in which the testing should be conducted.

• Operating System: (e.g., Windows 10, macOS Catalina, Ubuntu 20.04)
• Browser: (if applicable, e.g., Chrome, Firefox)
• Other relevant details: (e.g., specific hardware, configurations)

Checklist

• Test cases have been clearly defined.
• All necessary information for reproducing the issue or testing the feature has been provided.
• Expected behavior is well described.

Thank you for conducting this testing!