Skip to content

Conversation

@amyworrall
Copy link
Contributor

[Work in progress] new styles system

@facebook-github-bot
Copy link
Contributor

@amyworrall has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@amyworrall has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

static let strikethrough = StyleName(rawValue: "strikethrough")
static let code = StyleName(rawValue: "code")
static let superScript = StyleName(rawValue: "superScript")
static let subScript = StyleName(rawValue: "subScript")
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure what's the benefit of declaring these as constants in a struct. Is it to allow plugins to register their own styles (for extensibility)?

might be worth considering an enum:

enum Style: String, Codable {
  case bold
  case italic
  ...
  case subScript = "subScript"
} 

or if we need this to be extensible then:

enum Style: Codable {
  case bold
  case italic
  case custom(String) // can be extended by plugins

  init(from decoder: Decoder) throws {
    // manual decoding
  }
}
``

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The pattern I've used here is

I'm not sure what's the benefit of declaring these as constants in a struct. Is it to allow plugins to register their own styles (for extensibility)?

The pattern I've used here is the same as used for NodeType, etc…

I rather wanted to place all styles on equal footing, without favouring the built-in ones over whatever is added by a plugin…

@facebook-github-bot
Copy link
Contributor

Hi @amyworrall!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants