Task #4051
open
[ux, renderering] Consistent formatting on text fields.
Added by Marcin Kuzminski [CTO] over 8 years ago.
Updated about 7 years ago.
Estimated time:
(Total: 0.00 h)
Description
Currently we have various fields formatted and wrapped in markdown formatters.
- For comments we use rst or MD formatter
- For Commit messages we use urlify_commit_Message
- for readme we use formatter based on the file extensions
- for Pull requests we use Markdown/rst formatters
Some of those formatters are inconsistent, ie commit messages vs commit commits. We need a quick iteration and find a subset that would make all those behave consistent.
Functionality within text fields which should be included:
- consistent formatting based on chosen renderer in _admin/settings/visual
- @-mentions
- issue tracker patterns
- linkification of urls
Related issues
1 (1 open — 0 closed)
This is similar to an issue I wanted to bring up in refinement; I've prepared some notes about it when we're ready to tackle it.
- Target version changed from v4.3 to v4.4
- Subject changed from Consistent formatting on text fields. to [ux, renderering] Consistent formatting on text fields.
notes from refinement meeting 06.09.2016
- renderer is currently a global option but will be made per-repo
- file rendering should remain the same, based on file extension
- text fields should be the same everywhere; can be confusing if functionality is inconsistent
- need to make a list of all renderers
- implementation: flip flags to expose mentions, etc.
- Description updated (diff)
- Related to Task #4153: Optimize readme fetching by changing the system of readme detection added
- Target version changed from v4.4 to v4.5
- Target version changed from v4.5 to v4.6
- Target version changed from v4.6 to v4.7
- Target version changed from v4.7 to v4.8
- Target version changed from v4.8 to v4.10
- Target version changed from v4.10 to v4.11
Also available in: Atom
PDF