New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe indexer structure and list existing fetchers #1763
Conversation
Resolves #1628. A brief description of indexer structure is added to `README.md` of `indexer` application. Installation instructions are removed, as they don't make sense for sub-app of umbrella application.
Pull Request Test Coverage Report for Build e4eb5f55-b332-469e-a9a0-5c62fcd6e6de
💛 - Coveralls |
Documentation can be generated with [ExDoc](https://github.com/elixir-lang/ex_doc) | ||
and published on [HexDocs](https://hexdocs.pm). Once published, the docs can | ||
be found at [https://hexdocs.pm/indexer](https://hexdocs.pm/indexer). | ||
## Structure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can move this to some other markdown file? Because Readme
is meant to be an introduction to the project. This is some advanced stuff and it requires a knowledge of Elixir which most of our users don't possess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think moduledoc is the best place to put it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have README.md
in the root directory and each of the sub-apps.
I think that most users won't ever go past the root one, so it should contain instructions for them.
But if you actually go to read about a sub-app, you probably are already interested enough in how the app is structured, so it's a good place to put such description there.
Moreover, the only way to adequately read moduledoc
is compiling code documentation, which is not even done in our CI.
* master: (25 commits) Describe indexer structure and list existing fetchers (#1763) add more test cases fix CR issues add CHANGELOG entry do not hardcode values in tests fix credo add CHANGELOG entry add today's token balance from previous value add CHANGELOG entry fix gettext add label change package version download chrom directly fix command order fix script try using chrome headless for wallaby fix failing test update phantom js on circle ci bumbp cache version fix gettext ... # Conflicts: # apps/block_scout_web/priv/gettext/default.pot # apps/block_scout_web/priv/gettext/en/LC_MESSAGES/default.po
#1638-new-style-for-lukso-network * feature/#1476-add-styles-for-POSDAO-network: (25 commits) Describe indexer structure and list existing fetchers (#1763) add more test cases fix CR issues add CHANGELOG entry do not hardcode values in tests fix credo add CHANGELOG entry add today's token balance from previous value add CHANGELOG entry fix gettext add label change package version download chrom directly fix command order fix script try using chrome headless for wallaby fix failing test update phantom js on circle ci bumbp cache version fix gettext ... # Conflicts: # apps/block_scout_web/priv/gettext/default.pot # apps/block_scout_web/priv/gettext/en/LC_MESSAGES/default.po
Resolves #1628.
A brief description of indexer structure is added to
README.md
ofindexer
application.Installation instructions are removed, as they don't make sense for sub-app of umbrella application.
Checklist for your PR
CHANGELOG.md
with this PR