Skip to content
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

Merged
merged 2 commits into from Apr 16, 2019

Conversation

goodsoft
Copy link
Contributor

@goodsoft goodsoft commented Apr 16, 2019

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.

Checklist for your PR

  • I added an entry to CHANGELOG.md with this PR
  • If I added new functionality, I added tests covering it.
  • If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
  • I checked whether I should update the docs and did so if necessary

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.
@ghost ghost assigned goodsoft Apr 16, 2019
@ghost ghost added the in progress label Apr 16, 2019
@coveralls
Copy link

coveralls commented Apr 16, 2019

Pull Request Test Coverage Report for Build e4eb5f55-b332-469e-a9a0-5c62fcd6e6de

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 83.008%

Totals Coverage Status
Change from base Build e2904554-d9e2-419b-b8db-1e2519e5d9e0: 0.0%
Covered Lines: 4416
Relevant Lines: 5320

💛 - 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
Copy link
Contributor

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.

Copy link
Contributor

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.

Copy link
Contributor Author

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.

@goodsoft goodsoft merged commit ef1b0cd into master Apr 16, 2019
@ghost ghost removed the in progress label Apr 16, 2019
gabitoesmiapodo added a commit that referenced this pull request Apr 16, 2019
* 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
gabitoesmiapodo added a commit that referenced this pull request Apr 16, 2019
#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
@vbaranov vbaranov deleted the gs-indexer-description branch May 28, 2019 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create an inventory list of all fetchers in indexer
5 participants