TypeScript Parser Implementation

[Denny09310]

This PR aims to merge the new-parser branch with the main branch to leverage the new features provided by .NET 8. Additionally, we have replaced the old regex-based parser with a new TypeScript parser, ensuring enhanced performance and maintainability.

Changes Made:

1. Merged new-parser Branch with main:

   • Integrated the latest features and improvements from .NET 8.
   • Resolved merge conflicts to ensure compatibility with the main branch.

2. Replaced Old Regex Parser with New TypeScript Parser:

   • Removed the legacy regex parser implementation.
   • Integrated a new TypeScript parser for improved parsing capabilities.
   • Updated the relevant code sections to utilize the new parser.

3. Testing and Verification:

   • Executed all unit and integration tests to validate the changes.
   • Confirmed that all tests pass, ensuring the new parser works correctly.

Benefits:

• Enhanced Performance: The new TypeScript parser is more efficient and maintainable compared to the old regex-based implementation.
• Modern Features: Leveraging .NET 8 features enhances the application's performance and provides access to the latest framework improvements.
• Code Quality: Improved parsing logic with the new TypeScript parser, reducing potential bugs and increasing maintainability.

Testing:

• Unit Tests: All existing unit tests were run to ensure no regression issues were introduced. (This based on the tests done, there's much work to do to say that there are no potential regression issues)
• Integration Tests: Comprehensive integration tests were executed to verify the end-to-end functionality with the new parser.
• Manual Testing: Additional manual testing was conducted on critical paths to ensure stability and correctness.

How to Review:

1. Code Changes:

   • Review the commit history for detailed changes.
   • Pay special attention to the parsing logic modifications and test updates.

2. Testing:

   • Check the test results to confirm all tests pass.
   • Run additional tests if needed to verify specific scenarios.

3. Documentation:

   • Ensure that any relevant documentation is updated to reflect the changes, especially in areas related to the new parser.

---

Checklist:

• Merged new-parser branch with main.
• Replaced old regex parser with new TypeScript parser.
• Verified all tests pass.
• Updated documentation as needed.

[IEvangelist]

Hi @Denny09310 - since this is such a large change and based on a branch I already had let's target a PR to that branch, so that I can pull it down and test it out too.

[Denny09310]

Hi @Denny09310 - since this is such a large change and based on a branch I already had let's target a PR to that branch, so that I can pull it down and test it out too.

Yes, sorry I haven't noticed that I was targeting the branch 'main'. I've noticed some errors in the "SpeechSyntesis" package (I don't know if they were already present) that I should address asap

[IEvangelist]

Wow! That was a lot to review!! I really appreciate this. Before it goes to main, we'll need to rebase with main first - and there will be merge conflicts.