| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
The tagline led with Cloudflare, which names the origin rather than what someone gets: Durable Objects they host themselves, distributed, with no daemon to run and no database to add.
Greptile SummaryThe PR replaces the README's origin-focused tagline with a capability-focused description.
Confidence Score: 4/5The documentation claim should be corrected before merging because users can otherwise omit the required worker and leave durable asynchronous work pending indefinitely. The new tagline says no daemon is needed, while the gem's documented asynchronous features require a continuously running solid_objects start process. Files Needing Attention: README.md Important Files Changed
### Issue 1
README.md:5
**Daemon-free claim contradicts runtime requirement**
When users rely on this tagline for asynchronous or scheduled operations, the claim that no daemon is needed contradicts the required long-running `solid_objects start` worker, causing durable messages to remain pending indefinitely when that process is omitted.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: "Say what the gem is rather than what it ..." | Re-trigger Greptile |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Changes the README tagline:
to
The old line named where the idea came from. The new one names what someone gets: Durable Objects they host themselves, distributed, with no daemon to run and no database to add.
One thing left alone
solid_objects.gemspec carries the same sentence as spec.summary, which is what rubygems.org shows:
I left it, since changing a published package field is a bigger call than editing a README and was not part of the request. Say the word and I will match it here, or in its own change.