Skip to content

Conversation

@marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented May 2, 2024

Closes #1094

This change (choose at least one, delete ones that don't apply):

  • Breaks existing normative behavior (please add label "breaking")
  • Adds new normative requirements
  • Adds new normative recommendations or optional items
  • Makes editorial changes (changes informative sections, or changes normative sections without changing behavior)
  • Is a "chore" (metadata, formatting, fixing warnings, etc).

Implementation commitment (delete if not making normative changes):

If change is normative, and it adds or changes a member:

Commit message:

(Fill in. If making normative changes, describe exactly what the behavioral
difference will be.)

Person merging, please make sure that commits are squashed with one of the following as a commit message prefix:

  • chore:
  • editorial:
  • BREAKING CHANGE:
  • And use none if it's a normative change

Preview | Diff

@mgiuca
Copy link
Collaborator

mgiuca commented May 3, 2024

+1 to the general idea of this: it's overly restrictive and UAs should be able to choose the best icon of all the icons (assuming they follow the requirements of the "purpose" field).

@marcoscaceres marcoscaceres merged commit 2f54efe into main Jun 6, 2024
@marcoscaceres marcoscaceres deleted the icons branch June 6, 2024 23:01
github-actions bot added a commit that referenced this pull request Jun 6, 2024
SHA: 2f54efe
Reason: push, by marcoscaceres

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

Icon purpose "any" is confusing

4 participants