cibernox / cibernox/ember-power-select-with-fallback
Missing features list
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] Add rules `iphone` and `ipad`, and make `ios` being (`iphone` OR `ipad`)
- [ ] Add rules `android-phone` and `android-tablet`, and make `android` being (`android-hone` OR `android-tablet`)
- [ ] Create `phone` (`iphone` OR `android-tabled` OR `windows-phone`)
- [ ] Create `tablet` (`ipad` OR `android-tablet`)
- [ ] Make some `mobile-device` be `phone` OR `tablet`.
- [ ] Ensure passing a promise to options work.
- [ ] Validate that options don't have more that 1 leved deep groups (only in development)
- [ ] Warn if the user is specifying a custom `search` action
- [ ] Warn if the user is specifying a custom `matcher` function
- [ ] Add tests
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing rules, options, search, and matcher entry points in the repository, then inspect how current tests are organized. Clarify the rule names and relationships, including the apparent typos, before implementing the grouped mobile-device rules. Done means the requested option handling, development-only validation, warnings, and comprehensive tests are all defined and passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100