removing it

[vijaykiran225]

Purpose

Describe the problem or feature in addition to a link to the issues.

Approach

How does this change address the problem?

Is there a documented page to address the problem?

Solution

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[codecov-io]

Codecov Report

Merging #1 into temp will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             temp       #1   +/-   ##
=======================================
  Coverage   46.47%   46.47%           
=======================================
  Files           7        7           
  Lines         213      213           
  Branches        3        3           
=======================================
  Hits           99       99           
  Misses        114      114

---

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 915454f...0cef5d6. Read the comment docs.

[vijaykiran225]

Purpose

Describe the problem or feature in addition to a link to the issues.

Approach

How does this change address the problem?

Is there a documented page to address the problem?

Solution

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[vijaykiran225]

Hi vijaykiran225 , thanks for your PR .. your ratio is 1.0

[vijaykiran225]

Hi vijaykiran225 , thanks for your PR .. your ratio is 1.0

[vijaykiran225]

Hi vijaykiran225 , thanks for your PR .. your ratio is 1.0

[vijaykiran225]

Hi vijaykiran225 , thanks for your PR .. your ratio is 1.0