Content
View differences
Updated by Aleix Suau over 5 years ago
### **Environment**:
qa-edge
OpenProject 11.1.2
### **Steps to reproduce:**
1. Open work package in split screen.
2. Add comment and reference work package with ##.
### **Actual Behavior**
Work package referenced with ## not rendered (referencing with # works properly).
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20360/content"></div></figure>
### **Expected Behavior**
Work package referenced with ## not rendered properly.
### Development Notes
* We have two ways of handling wp mentions:
* Old: markdown contains '#id' '#id'
* This is also the way it works if we don't select the wp from the suggestions.
* New: markdown contains '<mention data-id...'
* Wp mentions:
* data-mention property has '@#id'
* Sometimes link contains undefined
* Sending a <mention> tag the
* Backend:
* Three different scenarios/responses:
\- If we add '#id' without choosing a suggestion (it is also the case for old mentions I guess), the wp link is shown in the display view but it is just a string in the editing view. Sample call:
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20533/content"></div></figure>
\- If we add '##id' without choosing a suggestion (the current issue), nothing is shown in the display view but the string is shown in the editing view.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20534/content"></div></figure>
\- If we choose an options suggestions, a 'mention' tag is added to the markdown and it is correctly displayed in both views (display and editing).
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20535/content"></div></figure>
* Issues:
* data-mention property has '@#id'
* Sometimes link contains undefined
qa-edge
OpenProject 11.1.2
### **Steps to reproduce:**
1. Open work package in split screen.
2. Add comment and reference work package with ##.
### **Actual Behavior**
Work package referenced with ## not rendered (referencing with # works properly).
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20360/content"></div></figure>
### **Expected Behavior**
Work package referenced with ## not rendered properly.
### Development Notes
* We have two ways of handling wp mentions:
* Old: markdown contains '#id'
* This is also the way it works if we don't select the wp from the suggestions.
* New: markdown contains '<mention data-id...'
*
* data-mention property has '@#id'
* Sometimes link contains undefined
* Sending a <mention> tag the
*
* Three different scenarios/responses:
\- If we add '#id' without choosing a suggestion (it is also the case for old mentions I guess), the wp link is shown in the display view but it is just a string in the editing view. Sample call:
\- If we add '##id' without choosing a suggestion (the current issue), nothing is shown in the display view but the string is shown in the editing view.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20534/content"></div></figure>
\- If we choose an options suggestions, a 'mention' tag is added to the markdown and it is correctly displayed in both views (display and editing).
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20535/content"></div></figure>
* Issues:
* data-mention property has '@#id'
* Sometimes link contains undefined