Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support complicationset folders #1051

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

Patrick-Kladek
Copy link

@Patrick-Kladek Patrick-Kladek commented Mar 9, 2023

  • I've started my branch from the develop branch (gitflow)
    • And I've selected develop as the "base" branch for this Pull Request I'm about to create
  • I've added an entry in the CHANGELOG.md file to explain my changes and credit myself
    (or added #trivial to the PR title if I think it doesn't warrant a mention in the CHANGELOG)
    • Add the entry in the appropriate section (Bug Fix / New Feature / Breaking Change / Internal Change)
    • Add a period and 2 spaces at the end of your short entry description
    • Add links to your GitHub profile to credit yourself and to the related PR and issue after your description

@Patrick-Kladek
Copy link
Author

I'm not sure if this is the right approach but it works for my use case and passes tests. If there is a better solution please point me in the right direction.

@Patrick-Kladek Patrick-Kladek marked this pull request as ready for review March 9, 2023 19:43
Copy link
Member

@djbe djbe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not very familiar with WatchOS complications, but from some quick googling:

  • In your project (info.plist), you point it at the right "group" in your asset catalog
  • I couldn't find any code samples where users load a complication asset programatically?

So I'm not sure if there's any point in adding support for this type of asset?

Note: also found that all docs mark complications as deprecated, and everything now should be done with WidgetKit. Does that framework also use complicationset assets?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to commit all these images? For our other image assets, we simply added 1 variation, which is enough.

Comment on lines +29 to +32
let children = try? folder.children()
let sorted = children?.sorted(by: <)

return (sorted?.compactMap { path in
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't change anything?

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.

None yet

2 participants