Skip to content
This repository has been archived by the owner on Jun 1, 2023. It is now read-only.

Group enum cases based on MARK comments #107

Open
sindresorhus opened this issue May 12, 2020 · 4 comments
Open

Group enum cases based on MARK comments #107

sindresorhus opened this issue May 12, 2020 · 4 comments
Labels
design Functionality with a design component enhancement New feature or request

Comments

@mattt mattt added the enhancement New feature or request label May 12, 2020
@mattt
Copy link
Contributor

mattt commented May 12, 2020

@sindresorhus Curious to know, do you have any thoughts about how MARK headings should relate to declaration type groupings? Should we treat them as peers / alternates or should we see the current "by type" grouping just as the default sections for when MARK headings aren't provided?

@mattt mattt added the design Functionality with a design component label May 12, 2020
@sindresorhus
Copy link
Author

My preference would be for them to be sub-headings under the Enumeration Cases section. Jazzy makes them top-level sections, which feels wrong to me.

@mattt
Copy link
Contributor

mattt commented May 13, 2020

@sindresorhus What if a section contains different kinds of symbols? For example:

enum E {

// MARK: Example

case c
func f() {}
}

Would they repeat for each kind of symbol, like this?

  • Cases
    • "Example"
      • c
  • Methods
    • "Example"
      • f()

@sindresorhus
Copy link
Author

Not sure, to be honest. I wouldn't use MARK like that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
design Functionality with a design component enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants