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

Adding support for different bullets by UL indentation level #1173

Closed
wants to merge 2 commits into from

Conversation

etoledom
Copy link
Contributor

This PR adds support for different bullets by UL indentation level for parity with Gutenberg Web:

The indented bullet will still be the same than the previous one (black bullet) until Android adds support for this too.

bullets

To test:

  • TextList.swift.
  • Search for return "\t\u{2022}" and change the unicode from 2022 to 25E6 (white bullet).
  • Open the example project and check that the indented bullets are the white dot. (as in the screenshot)

@SergioEstevao
Copy link
Contributor

Could this be done in a way that the bullet characters are configurable by the user of the library?

Copy link
Contributor

@diegoreymendez diegoreymendez left a comment

Choose a reason for hiding this comment

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

While the idea behind this PR is great, my understanding is that right now this change doesn't really change bullets at all - only the code in preparation for something that we're expecting will come up.

I understand and agree with the direction but my suggestion for this PR would be to either:

  • Make it possible to customize the bullets as @SergioEstevao is proposing, or
  • Merge this once we can swap to actually having a new bullet.

That said, @SergioEstevao 's suggestion sounds much better IMHO for a generic library.

@etoledom
Copy link
Contributor Author

I agree with you both!
Now that this is on its own PR, it makes sense to extend it to add a proper support for customizable bullets.

@SergioEstevao
Copy link
Contributor

@etoledom are you still working on this?

@etoledom
Copy link
Contributor Author

etoledom commented May 2, 2019

I haven't retaken this task yet.
Feel free to take it 😁

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.

3 participants