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

docs: fix broken references to plugin docs #2263

Closed
wants to merge 85 commits into from
Closed

docs: fix broken references to plugin docs #2263

wants to merge 85 commits into from

Conversation

jamesbooker
Copy link
Contributor

Proposed changes

Updates various readme.md files to resolve #2262

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Refactoring (improve a current implementation without adding a new feature or fixing a bug)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Build (changes that affect the build system)
  • Docs (documentation only changes)
  • Test (adding missing tests or fixing existing tests)
  • Other... Please describe:

Checklist

  • I have read the CONTRIBUTING documentation
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

paroxysm and others added 30 commits February 20, 2019 14:08
Merge branch 'develop' into 2.3
)

* refactor: replace micromatch with the more lightweight nanomatch

* fix(core-http-utils): remove non-existent deps

* fix(core-vote-report): add vision dependency

* Update create.ts
faustbrian and others added 6 commits March 18, 2019 14:39
If the search range is narrowed too much then the condition
"if (low + this.nAry >= high) {" would catch it and return. But it could
happen that we still have neighboring elements and that condition is not
true.

Check whether the probe declared that the highest match is at some
height and if we have probed the next height - the fact that the next
height was not declared a match, implicitly means that it is not a
match. And if we have two neighboring heights, the lower one a match and
the higher one not, then we don't need to search further and have the
final result.
Resolves #2262

Co-Authored-By: Brian Faust <faustbrian@users.noreply.github.com>
@ghost
Copy link

ghost commented Mar 19, 2019

Thanks for submitting this pull request! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

@ghost ghost added the Complexity: Low label Mar 19, 2019
@ghost
Copy link

ghost commented Mar 19, 2019

Your pull request doesn't follow our contribution guidelines. Please review and correct it.

Copy link
Contributor

@faustbrian faustbrian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rebase this to develop.

@ArkEcosystem ArkEcosystem deleted a comment Mar 19, 2019
@faustbrian faustbrian changed the title Broken docs links fixed docs: fix broken references to plugin docs Mar 19, 2019
@codecov-io
Copy link

Codecov Report

Merging #2263 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master   #2263   +/-   ##
======================================
  Coverage    79.2%   79.2%           
======================================
  Files         331     331           
  Lines        7924    7924           
  Branches     1125    1085   -40     
======================================
  Hits         6276    6276           
  Misses       1616    1616           
  Partials       32      32

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f271747...46093c9. Read the comment docs.

@jamesbooker
Copy link
Contributor Author

Please rebase this to develop.

I am struggling to do this, as it appears it's reverting dependencies to older versions? do I 'accept incoming changes'?

@jamesbooker
Copy link
Contributor Author

Please rebase this to develop.

I am struggling to do this, as it appears it's reverting dependencies to older versions? do I 'accept incoming changes'?

OK I have rebased, accepted changes from the develop branch and re-commited

@ghost
Copy link

ghost commented Mar 19, 2019

The ci/circleci: test-node11-2 job is failing as of 395e8c3fb502eec6e1f62d4858f86b5bfec5b99d. Please review the logs for more information.

Once you've pushed the fixes, the build will automatically re-run. Thanks!

@ghost
Copy link

ghost commented Mar 19, 2019

The ci/circleci: test-node10-2 job is failing as of 395e8c3fb502eec6e1f62d4858f86b5bfec5b99d. Please review the logs for more information.

Once you've pushed the fixes, the build will automatically re-run. Thanks!

@faustbrian
Copy link
Contributor

It looks like you merged instead of doing a rebase, might be easier to close the PR and resubmit it based on develop.

@jamesbooker
Copy link
Contributor Author

It looks like you merged instead of doing a rebase, might be easier to close the PR and resubmit it based on develop.

OK

@ghost
Copy link

ghost commented Mar 19, 2019

Your pull request has been closed, thank you for trying to solve an issue. If you think it was closed prematurely please provide additional information.

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.

Docs re-org broke some readme.md links in core
9 participants