Highlight community maintained recipes outside OpenRewrite org #131
Comments
|
I'm wondering if it'd make sense to add these community maintained recipes to the rewrite-recipe-markdown-generator 🤔 Any thoughts there @mike-solomon ? |
|
Would you mind expanding on what you mean by add these to the markdown generator @timtebeek ? If we are just making a page with links and a blurb, I’m not sure I see a need for automation on that front. It might be confusing to others if they edit the community page and then it gets overwritten. But maybe I’m missing something? |
|
Sure so for instance Axon Framework now has migration recipes: If we were to add There's some potential for confusion about which are community maintained, and which are OpenRewrite recipes. Some kind of note or label might be in order. Also not sure how these would tie in with the current categories, which might need attention. |
|
@timtebeek I didn't see any recipes in the public SaaS that matched If these community recipes aren't available in the SaaS, I feel like we shouldn't add them in the same section as the other recipes. Perhaps an entirely different tab with instructions for how to work with them. |
|
From Slack discussions - another point to consider: Some of the code we have will not work out of the box for external recipes. For instance, GitHub recipe links won't work as we've hard coded that to be very specific to OpenRewrite. I imagine other things may not work as well. If we did decide to add external recipes, some research would need to be done into what works and what we should change. |
As per https://github.com/gradle/actions/blob/main/dependency-submission/README.md Could help us both to analyze dependencies and get insight into dependents. - openrewrite/rewrite-docs#131
As per https://github.com/gradle/actions/blob/main/dependency-submission/README.md Could help us both to analyze dependencies and get insight into dependents. - openrewrite/rewrite-docs#131
|
As of recently we've started including some external recipe modules in rewrite-third-party, and from there add them to the generated documentation. We can evaluate and expand the above to include more recipes as helpful to our users. |
Aside from the recipes and use cases that we maintain, the wider community has also adopted OpenRewrite to do their own migrations. Notable instances of these are:
AtomicJar's rewrite-testcontainersCucumber-JVM: Add Cucumber-JVM migration module cucumber/cucumber-jvm-migration#1Collectors.toList()toStream.toList()Would be good to showcase these in some way in the documentation; I'm thinking a link just beneath the Recipe catalog link, that leads to a page with a bit of detail about each of these projects, and how they are using OpenRewrite. Possibly with a link inviting other projects to add themselves to the list with a pull request, such that it can grow over time.
That way we can show there's more to OpenRewrite than just what we maintain; plus it highlights that it has proven well enough to work for VMWare, Red Hat, AtomicJar, etc... that should tell people evaluation the project something as well.
Then perhaps in the future this can grow to encompass compatibility tests around our / their releases, and inclusion of compatible recipe collections in the SaaS. But all that can follow; a documentation page should do for now.
The text was updated successfully, but these errors were encountered: