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: Review docstrings #199

Merged
merged 4 commits into from
Jan 31, 2023
Merged

docs: Review docstrings #199

merged 4 commits into from
Jan 31, 2023

Conversation

YurelyCamacho
Copy link
Contributor

@YurelyCamacho YurelyCamacho commented Nov 28, 2022

Description

Review docstrings:
forecast_swiss.py
metrics.py
ngboost_models.py
preprocessing.py
epigraphhub_db.py
worldbank.py

Fixed docstring formatting as it was in most cases.

Checklist

  • I've read the CODE_OF_CONDUCT.md document.
  • I've read the CONTRIBUTING.md guide.
  • I've used pre-commit hook locally.
  • I've written tests for all new methods and classes that I created.
  • I've written the docstring in Google format for all the methods and classes that I used.
  • Semantic-release prefix title used (case sensitive):
    • Use the prefix chore(docs): for Examples / docs / tutorials / dependencies update
    • Use the prefix fix: for a bug fix
      (non-breaking change which fixes an issue).
    • Use the prefix chore(improvement): for an improvement
      (non-breaking change which improves an existing feature).
    • Use the prefix feat: for a new feature
      (non-breaking change which adds functionality).
    • Use the prefix BREAKING CHANGE: for a breaking change
      (fix or feature that would cause existing functionality to change).
    • Use the prefix chore(security): for a security fix.

Note: The title prefix can be also expanded with more information
inside the parenthesis. Some examples for a full title (prefix + message):

  • fix(login): Fix the login page.
  • feat(forecast): Add a weather forecast page.
  • chore(security-login): Add a weather forecast page.

@@ -1,7 +1,6 @@
"""
Last change on 2022/09/22
Comparing Colombia Governmental COVID data consists in a step before pushing it to
the SQL Database. Is responsible for retrieving the last date in both CSV and SQL table.
Comparing Colombia Governmental COVID data consists in a step before pushing it to the SQL Database. Is responsible for retrieving the last date in both CSV and SQL table.
Copy link
Member

Choose a reason for hiding this comment

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

any reason to keep the line so long?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, locally it does not appear like that.

@@ -59,14 +61,17 @@ def _table_last_update() -> datetime:

def _web_last_update() -> datetime:
"""
This method will request the maximum date found in Colombia data through Socrata API
and returns it as a datetime object for further evaluation.
This method will request the maximum date found in Colombia data through Socrata API and returns it as a datetime object for further evaluation.
Copy link
Member

Choose a reason for hiding this comment

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

please keep the line with less than 80 characters (<=79)

Copy link
Member

@xmnlab xmnlab left a comment

Choose a reason for hiding this comment

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

I've not read all the changes .. but in general .. it looks good to me.
thanks for working on that.

@eduardocorrearaujo could you review this one?

@@ -127,19 +135,25 @@ def search_in_database(keyword):


def search_in_indicators(keyword, db=2):

Copy link
Member

Choose a reason for hiding this comment

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

I think we don't need this empty line here

@@ -151,29 +165,36 @@ def search_in_indicators(keyword, db=2):


def get_worldbank_data(ind, country, db=2, time="all", columns=None):

Copy link
Member

Choose a reason for hiding this comment

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

same here

@github-actions
Copy link

Stale pull request message

@xmnlab
Copy link
Member

xmnlab commented Jan 30, 2023

Ping @eduardocorrearaujo @fccoelho

@fccoelho
Copy link
Contributor

It is looking good. We can merge it

Copy link
Contributor

@eduardocorrearaujo eduardocorrearaujo left a comment

Choose a reason for hiding this comment

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

It looks good. Thank you @YurelyCamacho

@xmnlab xmnlab changed the title Review docstrings docs: Review docstrings Jan 31, 2023
@xmnlab xmnlab merged commit ec69133 into thegraphnetwork:main Jan 31, 2023
@github-actions
Copy link

github-actions bot commented Feb 7, 2023

🎉 This PR is included in version 2.0.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

fccoelho pushed a commit that referenced this pull request Feb 14, 2023
* Review docstrings

* Review doscstring

* Arrangement of number of characters in the lines

* Update worldbank.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants