Skip to content

Conversation

@alsoto25
Copy link
Contributor

@alsoto25 alsoto25 commented Sep 2, 2025

Description

Fixing a few issues found on the repo. Initially I had each fix in a different branch, however since they were made before the testing branch was added, each branch had a lot of conflicts, so I decided to just compile all the changes into a single conflicts for each branch.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Refactoring (non-breaking change with no user-facing impact)
  • Breaking change (fix or feature that changes existing behavior)
  • Documentation update
  • Configuration (changes to build setup, tooling, or CI/CD)
  • Chore (maintenance, code cleanup, or minor non-functional tasks)
  • Test (adding or updating tests)

Related Issues

Testing

Tested locally using the dev environment
Also tested with the Playwright automated tests.

@alsoto25 alsoto25 self-assigned this Sep 2, 2025
Since this is a mostly functional library, there isn't a real benefit on running tests on multiple browsers. By removing the other browsers, we're able to test faster and the Github Action doesn't take as long
@Brian06 Brian06 merged commit 8c6bc03 into ltvco:main Sep 4, 2025
2 checks passed
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.

3 participants