Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
README.md needs an update
See original GitHub issueThe Architecture Overview in the README mentions the ResourceProcessor which no longer exists.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Quickly generate or update your project's README.md - GitHub
Quickly generate or update your project's README.md - GitHub - update-readme/update-readme: Quickly generate or update your project's README.md.
Read more >Should I update README.md when I adding new features to ...
I add a new feature to an open source project in Github that have no CONTRIBUTING.md. Should I explain my feature in README.md...
Read more >How to Create a Self-Updating README.md for Your GitHub ...
First thing first, to unlock this feature, you need to create a new repository. It needs to be named the same name as...
Read more >How I Built A Self-Updating README On My Github Profile
GitHub profile READMEs are a new feature that allows users to have the content of a README markdown file rendered at the profile...
Read more >How to Update a GitHub Profile README Automatically
Based on how your dates are formatted, you might need to update the regular expression. import feedparser def fetch_writing(): entries = feedparser.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Maybe we should try to be more concise and avoid pointing to actual class names.
Having a general overview should be enough. And maybe point to the root of a very simple extension that we could give as an example.
Moving that to
first public releaseas we don’t want the release to be done with outdated information in the README.Maybe it should be an overview of the final architecture with notes about things that are temporarily different or not implemented yet.