Like it always felt a bit like a hack needing to add a client component to handle redirects after submitting a form. But RWSDK gives a pretty elegant solution.
And that's just one of many intuitive features of RWSDK. I also like the `useSyncedState` hook they made that makes it very trivial to make real time communication between clients, for something like say, a chat room. https://docs.rwsdk.com/experimental/realtime/
I also dogfooded a reporter I've been working on with the initial v0 tutorial for this. Which then I rewrote that tutorial to demonstrate TDD principles for the v1-beta (to my knowledge there are no breaking changes between v1-beta and the final release, but I'll be going through later to confirm that.) https://www.test2doc.com/docs/tutorial-1
So last year the Redwood team, after launching v0 also launched a tutorial to built a non-trivial webapp using their framework. But they're now getting ready for v1 and introduced a few breaking changes so made their tutorial obsolete.
I dogfooded my Playwright reporter on this tutorial, so figured I'd rewrite it for v1 and I wanted to make a tutorial to teach test-driven development too, since I seemed to see a few devs say that testing was a reason they weren't interested in my reporter that generates docs from tests.
Anyway, I completed it earlier this week.
So if you want to learn RedwoodSDK, learn a bit more about Playwright testing, and wanting to learn how you can turn your tests in to living documentation, give it a shot.
That's great to know. I was thinking about tackling this from the highest level of abstraction first, so the user interface. I plan on supporting Playwright first for MVP, and then expanding in to Cypress, and maybe even unit testing frameworks.
I feel like backend API documentation is kind of handled with things like Swagger.
How do you think your in house solution compares to something like Swagger or Javadoc?
One of my personal fears (which might be a bit unfounded) since Swagger and Javadoc are generated based off of code comments, and not tests, and there is a possibility that they could get out of sync with implementation. But that might be unfounded. When I worked on Java and wrote unit tests and generated Swagger docs, we never actually ran in to the problem of these things becoming out of sync.
I theorize that the front end isn't as well disciplined as it is in the backend world as well. Which is where I think this idea of Test2Doc will really shine.
Anyway, the ball is currently in the employer's court and the idea of exchanging one faceless master for another doesn't immediately sound appealing, so I figured I'll try to solve a pain point that I've experienced for a while.
Full transparency: I don't have the MVP working just yet. But what I'm trying to do is gauge genuine demand for an idea before I go all in.
*What if we could generate documentation from tests?*
Having documentation become stale sucks. Keeping docs up to date is hard.
Tests already verify the actual behavior of your system, so they can't lie about what your code does. They're living documentation that's always in sync with reality.
What if we could turn tests into docs that non-technical team members can actually use, or even the public?
It'd be great for onboarding new team members, giving product documentation for everything that's already been implemented, and–assuming we can come up with some best practices on how to write these tests–can even help reduce help desk calls as public facing documentation can self update on every deploy.
And I think we can. I'm currently playing around with this, but the theory is I can use Playwright, create a custom reporter for it, and it'll generate markdown you can use in something like Docusaurus.
That's not the paid product. That'll be an open source library that I'll give away.
But what I want to know is, would you be interested in paying for a SaaS platform that will host the docs and have integrations with:
* Github - allow non-technical to make PRs to update copy (code is the source of truth)
* JIRA – Link to the original requirements and vice versa
* Google Doc style comments for collaborative feedback
* On-prem support if you're paranoid and want to keep your secret docs away from public eyes
Check out my totally original unique landing page if these pain points are something you can relate to and I'm looking for feedback on this idea. Does it have legs? Does this address a problem you see at your company? Do you want help writing better tests to have better documentation for your codebase?
And now with v1 there are some really logical patterns that I really enjoy.
Like returning Responses from server actions and then the framework automatically handles things like redirecting. https://docs.rwsdk.com/core/react-server-components/#returni...
Like it always felt a bit like a hack needing to add a client component to handle redirects after submitting a form. But RWSDK gives a pretty elegant solution.
And that's just one of many intuitive features of RWSDK. I also like the `useSyncedState` hook they made that makes it very trivial to make real time communication between clients, for something like say, a chat room. https://docs.rwsdk.com/experimental/realtime/
I also dogfooded a reporter I've been working on with the initial v0 tutorial for this. Which then I rewrote that tutorial to demonstrate TDD principles for the v1-beta (to my knowledge there are no breaking changes between v1-beta and the final release, but I'll be going through later to confirm that.) https://www.test2doc.com/docs/tutorial-1