Project

General

Profile

Task #4051

[ux, renderering] Consistent formatting on text fields.

Added by Marcin Kuzminski [CTO] about 5 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
06.09.2016
Due date:
% Done:

50%

Estimated time:
(Total: 0.00 h)
Sorting:
Commit Number:

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

Subtasks

Task #4215: [ux] identify all text renderersClosedLisa Quatmann06.09.2016

Actions
Task #4216: [ux, renderers] implement consistent rendering for text fieldsNew06.09.2016

Actions

Related issues

Related to RhodeCode CE/EE - Task #4153: Optimize readme fetching by changing the system of readme detectionResolvedJohannes Bornhold05.08.2016

Actions
#1

Updated by Lisa Quatmann about 5 years ago

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.

#2

Updated by Marcin Kuzminski [CTO] about 5 years ago

  • Target version changed from v4.3 to v4.4
#3

Updated by Lisa Quatmann about 5 years ago

  • 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.
#4

Updated by Lisa Quatmann about 5 years ago

  • Description updated (diff)
#7

Updated by Lisa Quatmann about 5 years ago

  • Related to Task #4153: Optimize readme fetching by changing the system of readme detection added
#8

Updated by Marcin Kuzminski [CTO] about 5 years ago

  • Target version changed from v4.4 to v4.5
#9

Updated by Marcin Kuzminski [CTO] almost 5 years ago

  • Target version changed from v4.5 to v4.6
#10

Updated by Marcin Kuzminski [CTO] over 4 years ago

  • Target version changed from v4.6 to v4.7
#11

Updated by Marcin Kuzminski [CTO] over 4 years ago

  • Target version changed from v4.7 to v4.8
#12

Updated by Marcin Kuzminski [CTO] over 4 years ago

  • Target version changed from v4.8 to v4.10
#13

Updated by Marcin Kuzminski [CTO] about 4 years ago

  • Target version changed from v4.10 to v4.11

Also available in: Atom PDF