Hi All - re the recent polly for discontinuing/dep...
# ui
l
Hi All - re the recent polly for discontinuing/deprecating markdown support in the description fields in the UI: We currently bulk add metadata to Datahub by importing CSVs containing metadata. We typically apply encapsulate text we put in the CSVs with mark down format/syntax so it is rendered in markdown format on the UI. if the decision to deprecate markdown support is made, will that mean that even if we format text in CSVs in markdown, it won't be displayed in markdown format in the UI?
b
hey Divy! great question - with a new text editor and new format for supporting rich text, we will certainly remain backwards compatible with markdown. So if you post markdown documentation to entities in datahub, we will still be able to display the markdown as desired. However, with the move to a new format (to support more functionality in documentation editing) we believe we may simply convert markdown to the new format when you edit through the UI. So as far as things go in the UI, people shouldn't know or care what format their documentation is really in!
I think the main concern with the polly is whether or not people are reading this markdown from datahub through APIs and not the UI, to determine if moving to a new format in general would break workflows for people in that way. But if people have existing documentation in markdown or post markdown, we will still be able to support rendering that through the datahub UI just fine