[$250] Live markdown for workspace description

[roryabraham]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1711641837108169

Action Performed:

1. Create a workspace if you don't already have one
2. Open workspace settings
3. Click on the input for workspace description and start typing markdown in there

Expected Result:

The markdown styling should render in real-time, as it does for the main chat composer.

Actual Result:

No live markdown formatting.

Workaround:

n/a

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01feb88466d128ac03
• Upwork Job ID: 1773388688826933248
• Last Price Increase: 2024-03-28

Issue Owner

Current Issue Owner: @twisterdotcom

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01feb88466d128ac03

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav (External)

[melvin-bot]

Triggered auto assignment to @twisterdotcom (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.

[melvin-bot]

⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

[nkdengineer]

I'd like to work on this if it's open for contributors 👍

Proposal

Please re-state the problem that we are trying to solve in this issue.

No live markdown formatting currently for workspace description

What is the root cause of that problem?

This is new feature.

What changes do you think we should make in order to solve the problem?

Use RNMarkdownTextInput, just like we're doing for Composer here, we'll need to apply it to the workspace description input here, additional style changes will be needed.

What alternative solutions did you explore? (Optional)

NA

[melvin-bot]

Upwork job price has been updated to $250

[roryabraham]

@nkdengineer friendly piece of feedback: please take the time you need to add a bit of detail to the proposal. The practice of "speedrun" proposals where you post quickly then edit it incrementally isn't something I like to see

[melvin-bot]

📣 @nkdengineer You have been assigned to this job!
Please apply to the Upwork job and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Once you apply to this job, your Upwork ID will be stored and you will be automatically hired for future jobs!
Keep in mind: Code of Conduct | Contributing 📖

[ZhenjaHorbach]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Live markdown for workspace description

What is the root cause of that problem?

New feature

What changes do you think we should make in order to solve the problem?

To fix this issue we can need make some changes

For details page we use InputWrapperWithRef

App/src/pages/iou/request/step/IOURequestStepDescription.js

Lines 191 to 209 in c64770e

	<InputWrapperWithRef
	InputComponent={TextInput}
	inputID={INPUT_IDS.MONEY_REQUEST_COMMENT}
	name={INPUT_IDS.MONEY_REQUEST_COMMENT}
	defaultValue={currentDescription}
	label={translate('moneyRequestConfirmationList.whatsItFor')}
	accessibilityLabel={translate('moneyRequestConfirmationList.whatsItFor')}
	role={CONST.ROLE.PRESENTATION}
	ref={(el) => {
	if (!el) {
	return;
	}
	inputRef.current = el;
	updateMultilineInputRange(inputRef.current);
	}}
	autoGrowHeight
	containerStyles={[styles.autoGrowHeightMultilineInput]}
	shouldSubmitForm
	/>

So we need change InputComponent={TextInput} to InputComponent={RNMarkdownTextInput}

What alternative solutions did you explore? (Optional)

NA

[roryabraham]

Also note that we should wait for live markdown web to land on production before merging a PR here

[nkdengineer]

@roryabraham Thanks for the feedback! I'll take note of it 🙏

[mananjadhav]

I can see the proposal was already accepted and @nkdengineer was assigned. @roryabraham Do we want to hold the issue by linking the live markdown issue here?

[nkdengineer]

@mananjadhav The PR is here #39686.

[melvin-bot]

Triggered auto assignment to @blimpich, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[melvin-bot]

This issue has not been updated in over 15 days. @mananjadhav, @twisterdotcom, @blimpich, @nkdengineer eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[mananjadhav]

@twisterdotcom This is ready for payout. This is a feature request and hence doesn't have an offending PR.

But I think we should copy the Test steps from the PR as regression steps?

[blimpich]

Sorry it seems the automation didn't work. Payment should be out shortly. 👍

cc: @twisterdotcom

[twisterdotcom]

Okay, payouts just $250 for @mananjadhav and @nkdengineer right?

[mananjadhav]

Yes @twisterdotcom

[JmillsExpensify]

$250 approved for @mananjadhav

[twisterdotcom]

Payment Summary:

• @mananjadhav paid $250 via NewDot requests (C+)
• @nkdengineer paid $250 via Upwork here (Contributor)

[mananjadhav]

@twisterdotcom Not fair!! $250 for me and $2500 for @nkdengineer ? 🤣 🤣

[blimpich]

💰🤑💸

[twisterdotcom]

😂 wooops. Just had to check the contract too make sure I didn't mess that one up too. Just a typo!

[nkdengineer]

@twisterdotcom Offer accepted 🙏