OpenMetadata VS react-markdown

In this blog post, I have demonstrated how I addressed the challenge of dynamically adjusting the height of a textarea element based on its content, preventing the need for vertical scrolling in the title section of the OpenMetadata Knowledge article page.

How does this compare with https://github.com/open-metadata/OpenMetadata

u/cmcau try https://open-metadata.org much easier to setup , for details https://docs.open-metadata.org and for any support https://slack.open-metadata.org

Then, a pool of tools appeared on the market with features that allow covering some of the challenges cited, especially those related to data cataloging. Informatica's tool is perhaps the best known among the licensed. Among the open source tools, I highlight Data Hub (www.datahubproject.io) developed on LinkedIn, Open Metadata (https://open-metadata.org/) and Amundsen (https://www.amundsen.io /) powered by Lyft. In addition to cataloging and discovering data artifacts, these tools allow for a view of data lineage, including technical documentation and business terms, and building relationships between data artifacts. Also, it is possible to register data owners, the people responsible for the data in those tools. This greatly facilitates access request and evaluation process (which today is a major bottleneck).

Probably, in order to have it integrate with tools like OpenLineage and OpenMetadata and such I will have to make open-source contributions.

We are the team behind OpenMetadata . Our mission is to build a centralized metadata platform that offers data discovery, collaboration, governance and quality. We believe that having tool for each of these categories not only result user frustration but metadata silos.

As anyone ever tried open metadata for data QA testing? Curious about that https://open-metadata.org/

We're looking to PoC https://open-metadata.org/ shortly

Hello everyone, I'm looking for an open-source data lineage app (e.g. tokern, datahubproject, openmetadata).

We at OpenMetadata(https://open-metadata.org) use JsonSchema extensively to define the metadata standards. JsonSchema is one of the reasons we are able to ship and get the project to what it is today in quick time. More about it here https://www.youtube.com/watch?v=ZrVTZwmTR3k

This error related to the ReactMarkdown component and the useDisclosure hook in the @chakra-ui/react.

The example above uses react-markdown, but you can use any library you want to render the markdown content. You can also use a transform function to modify the markdown content during the build process. Here is an example that uses MDX to compile the markdown content.

21.react-markdown

github.com/remarkjs/react-markdown - Biblioteca para renderizar markdown em nosso componente react.

3. Setup react-markdown and @tailwindcss/typography

The OpenAI API returns responses in Markdown format. To display responses from the chat, which contain formatting, I used the ReactMarkdown component. For code inserts, I used React Syntax Highlighter.

You can also choose to convert this to Markdown and use our Markdown metafield instead if you prefer, just note you’ll need to install a markdown package to do so. The article Building React Components from headless CMS markdown is a great read about how a package like React Markdown parses markdown from a headless CMS, and explains how to render markdown in a Next.js application.

Thank you! It's actually all thanks to the amazing react-markdown package (https://github.com/remarkjs/react-markdown), can't take any credits there :')

Perhaps something like a markdown renderer. There are plenty of projects that can render markdown, so you could store your blogs that way instead.