Skip to content

Order of attributes matters to the platform analyzer? #105423

Open

Description

@ericstj

In #105409 @akoeplinger needed to reorder platform attributes to fix an issue. I'm surprised our analyzer depends on the ordering of attributes. It's not a common characteristic of our API for order of attributes to matter. Is this intentional @buyaa-n @jeffhandley?

Reference: dotnet/roslyn-analyzers#5266

Activity

  1. ghost added
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Jul 24, 2024
  2. added
    code-analyzerMarks an issue that suggests a Roslyn analyzer
    untriagedNew issue has not been triaged by the area owner
    and removed
    untriagedNew issue has not been triaged by the area owner
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Jul 24, 2024
  3. dotnet-policy-service commented on Jul 24, 2024

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @dotnet/area-system-runtime
    See info in area-owners.md if you want to be subscribed.

  4. added this to the Future milestone on Jul 27, 2024
  5. added and removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 27, 2024
  6. buyaa-n commented on Aug 2, 2024

    @buyaa-n
    Contributor

    In general order doesn't matter, it probably because of related platforms handling, as there is workaround @akoeplinger I assume this is not required for 9.0

  7. self-assigned this
    on Aug 2, 2024
  8. akoeplinger commented on Aug 2, 2024

    @akoeplinger
    Member

    correct, this is not needed for 9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions