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

fixes 487 #564

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

fixes 487 #564

wants to merge 4 commits into from

Conversation

deven367
Copy link

@deven367 deven367 commented May 30, 2024

This PR is a continuation of the previous PR #488. The PR closes #487 and closes #488.

Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

@deven367
Copy link
Author

deven367 commented May 30, 2024

H/T to @Salehbigdeli for fixing the issue. I created a new PR because I could not push to the existing PR in #488.

@jph00 can you take a look at this?

@jph00
Copy link
Contributor

jph00 commented May 30, 2024

Thank you! The fastcore CI test can be ignored -- that was my fault and it's fixed now. Can you check the nbdev integration test? Does this PR change the behavior in a user-facing way?

@deven367
Copy link
Author

@jph00 I don't think the PR changes the behavior in a user facing way.

The integration test fails due to a missing statement in Returns in while processing the DocmentTbl for the function

def _f(a,
        b, #param b
        c  #param c
       ): ...

The variable

_exp_res2 = """
|    | **Details** |
| -- | ----------- |
| a |  |
| b | param b |
| c | param c |
"""

should be

_exp_res2 = """
|    | **Details** |
| -- | ----------- |
| a |  |
| b | param b |
| c | param c |
| **Returns** |  |
"""

So the functions that don't have a specific return type, should they have a returns in the DocmentTbl?

@jph00 jph00 closed this May 31, 2024
@jph00 jph00 reopened this May 31, 2024
@jph00
Copy link
Contributor

jph00 commented Jun 1, 2024

I think it must be this PR that's causing the test failure. Other PRs to fastcore the last few days haven't triggered it, and this PR is changing the anno result for 'returns' to an empty string. Could you possibly take a closer look?

@deven367
Copy link
Author

Hi @jph00, I tried to make sense of the failing test case, but I can't understand how is anno result and return is being populated 😅

@deven367 deven367 changed the title Fixes 487 fixes 487 Jun 18, 2024
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.

using *args with @call_parse
3 participants