Emelia Smith
Emelia Smith
We'd use https://github.com/codemod-com/codemod to set it up. Which appears to be the "paved" path for doing codemods, as it's what's done for react, next.js and [node.js](https://app.codemod.com/registry?q=scope%3Anodejs)
Apparently it'd be: ```yaml # main-rule.yml # Simple rule to find @fedify/fedify/x/ imports (for search purposes) id: find-fedify-imports language: tsx rule: kind: string regex: '@fedify/fedify/x/\w+' inside: any: - kind: import_statement...
@dahlia I think it'd probably make sense to have the codemods in a separate repository, so `fedify-dev/codemods`?
@dahlia I'm not sure how that'll play with the codemod package
@dahlia yeah, that was the impression I got.
What about called it: `place.stream.delegation.impersonate` ? Though I'm hesitant really to ever suggest impersonation. I do still think this would be better as: - `place.stream.moderation.permission` - this would fit with...
Oh, and be sure to create a rewriter for all v1 records to v2
So my take on this after some consideration is that we probably shouldn't be extracting random links from the `content` property and then using those to generate previews, instead we...
Mirroring from the Mastodon PR: > I'd probably say an `attachment` type of `Link` is correct, however, for link previews, I suspect the answer would be adding an additional `preview`...
Whilst you could use a `Object`-derived type, this would probably imply that the object exists (even though it wouldn't be dereferenceable), so I think `Link` is probably safer along with...