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

refactor the TextareaWithImageUpload component to instead be MarkdownEnabledTextarea #39333

Merged
merged 5 commits into from
Mar 8, 2021

Conversation

Hamms
Copy link
Contributor

@Hamms Hamms commented Mar 4, 2021

A component which can programmatically add a number of different kind of features like ImageUpload. Also expand it to support Resource Links in addition to image uploads.

Testing story

Added a unit test, updated existing.

PR Checklist:

  • Tests provide adequate coverage
  • Privacy and Security impacts have been assessed
  • Code is well-commented
  • New features are translatable or updates will not break translations
  • Relevant documentation has been added or updated
  • User impact is well-understood and desirable
  • Pull Request is labeled appropriately
  • Follow-up work items (including potential tech debt) are tracked and linked

…ownEnabledTextarea`

A component which can programmatically add a number of different kind of features like ImageUpload
@Hamms Hamms requested a review from a team March 4, 2021 20:50
@Hamms Hamms marked this pull request as ready for review March 4, 2021 20:52
</div>
);
}
}
Copy link
Member

Choose a reason for hiding this comment

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

Sorry for the late request, but would you be willing to do some git-fu like git mv TextareaWithImageUpload.jsx MarkdownEnabledTextarea.jsx to preserve revision history and make diffs easier to see, now and in the future? (here and below for test file) Open to reasons we might not want to do this, but would prefer this pattern if there is no reason not to.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's already the state of the current revision history. There were just enough edits made to the files after moving them that they show up as different files in the overall diff, but if you examine the diff for the first commit individually you'll see what you're looking for

@Hamms Hamms merged commit 920eacd into staging Mar 8, 2021
@Hamms Hamms deleted the generalize-markdown-editor-components branch March 8, 2021 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants