Filings UI Refactor tests to support switch to composition API
Open
ENTITY - DO NOT USE
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Currently some tests in the Filings UI are relying on data objects that are only available to the options api so upon switching API's the unit tests will break.
Refactoring the tests will make going to the composition API much easier.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Filings UI unit tests that rely on data objects available only through the Options API. Review how those tests access component data and identify the changes needed for Composition API compatibility. Done means the tests no longer depend on Options API-only objects and continue to pass during the API switch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100