bfastts: allow a vector for type
Open
bug
good first issue
- Dominant language
- R
- Stars
- 53
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
By default `bfastts` will fail with a cryptic message if no `type` is supplied. It should either give a reasonable message or assume `irregular` (or `regular` if #2 is implemented).
Contributor guide
Research direction
Start at the bfastts entry point and trace how a missing type is handled. Determine the expected behavior between a helpful error and assuming irregular, then verify that the no-type case no longer produces a cryptic failure; the regular default depends on issue #2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100