feat: leverage `EntityStringQuery`

Open
#31 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
43/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ios, swift
Domain
frontend, mobile

Research direction

Search the iOS app for the existing username entry flow and inspect how it stores or passes usernames to widgets. Read the EntityStringQuery API and check its iOS 16.0+ requirement against the app’s deployment target. Done means users can select previously added or widget-entered usernames and still enter arbitrary ones, with the iOS version constraint handled.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Describe the solution you'd like
EntityStringQuery is a great API that will allow:

  • provide usernames a user added in the app earlier
  • provide usernames a user entered in other widgets
  • enter arbitrary usernames (as right now)
  • something else (requires creativity 😄)

Implementing EntityStringQuery will provide better user experience.

Additional context
A downside is that EntityStringQuery requires iOS 16.0+.

Dominant language
Swift
Stars
401
Forks
39
Avg merge
9m
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from latelunchapps/github-contributions-ios

All issues in latelunchapps/github-contributions-ios

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.