Fixed #26975 -- Clarified how Django looks for fixture files. #16104
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello! Thank you for your contribution 💪
As it's your first contribution be sure to check out the patch review checklist.
If you're fixing a ticket from Trac make sure to set the "Has patch" flag and include a link to this PR in the ticket!
If you have any design or process questions then you can ask in the Django forum.
Welcome aboard ⛵️!
filiplajszczak
force-pushed
the
ticket-26975
branch
from
91bf11e to
db8af19
Compare
filiplajszczak
force-pushed
the
ticket-26975
branch
from
db8af19 to
9e84655
Compare
felixxm
changed the title
felixxm
force-pushed
the
ticket-26975
branch
from
9e84655 to
e471f8c
Compare
|
@filiplajszczak Thanks for this patch 👍 Welcome aboard ⛵ I pushed tiny edits. |
Co-Authored-By: Daniel Brotsky <dev@brotsky.com>
felixxm
force-pushed
the
ticket-26975
branch
from
e471f8c to
fe6f4be
Compare
|
@felixxm Commit message is definitely better now. I was hesitant about |
|
@filiplajszczak I much appreciate that you picked this up and fixed it; I got busy at work (a long time ago) but always felt bad that I never got back to it. I'm very appreciative of the co-author credit. |
Explain the different effects of relative and absolute paths on
loaddata.Suggest that fixture files be namespaced, which makes the documentation for fixtures consistent with that for templates and static files.
Based on previous proposal from PR #6996 by @brotskydotcom made more howto-like and less reference-like.