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

Use field.name for DeferredAttributes for Django 3.x, fixes #20 #21

Merged
merged 1 commit into from
Jan 16, 2020

Conversation

miterion
Copy link
Contributor

@miterion miterion commented Dec 28, 2019

This PR should fix #20

I did not found a way to force the usage of a DeferredAttribute and could therefore not write a test case.

@codecov-io
Copy link

codecov-io commented Dec 28, 2019

Codecov Report

Merging #21 into master will decrease coverage by 0.83%.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master   #21      +/-   ##
=======================================
- Coverage   57.84%   57%   -0.84%     
=======================================
  Files           6     6              
  Lines         204   207       +3     
=======================================
  Hits          118   118              
- Misses         86    89       +3
Impacted Files Coverage Δ
sphinxcontrib_django/docstrings.py 41.44% <0%> (-0.84%) ⬇️

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 5508cf0...9653a19. Read the comment docs.

@vdboor vdboor merged commit 5a63b0b into sphinx-doc:master Jan 16, 2020
@vdboor
Copy link
Contributor

vdboor commented Jan 16, 2020

Thanks for the fix!

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.

AttributeError for DeferredAttribute objects in Django > 3.0
3 participants