Results 18 comments of Brian Phillips

Yeah, the purpose of the tool I added was to convert formatted text (rich text) that a user might copy from a non-HTML document (i.e. a Google Doc) into Markdown....

Good idea, I will see if an option can be passed in to the default editor to modify the "paste" button (or perhaps to ad a "Paste with formatting" button?)...

Personally, I prefer keeping the metadata in the catalog itself (whether in the source `catalog-info.yaml` files or as an enrichment step via a CatalogProcessor) as this makes it simpler for...

I think the UI sounds useful and I think that storing it in the DB and then merging that into the catalog data via a processor would be a straightforward...

> I think my only concern is how this would work with those of us who have our catalog ingestion set to read-only. Would it be possible to automatically open...

I'm still getting the same error with backstage v1.28.0 and `@drodil/[email protected]`. Downgrading to `1.20.5` fixes it of course but I was expecting the `1.28.0` release to fix it. Is there...

I am still regularly running into this issue (probably 2-3 times per month) where there are duplicate rows in the `search` table and I have to manually delete them.