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
oscar_fork_app issue when forking to a current dirrectory using dot(.) #1717
Comments
Hello @manevant, sorry for being slow to get back to you. Thank you for the PR as well. Can you explain why you'd like to fork the app in the top level folder? I think it's pretty common to have an Could you try to explain your motivation a bit more? Related: I do think we have an issue where we should be looking at absolute paths, and expand relative paths into such. But I'm not sure right now. |
Hello @maikhoepfel ! Only one reason why i want to copy forked apps into a root directory - our project guideline(btw i dont agree them :) ) What do you think about that? PS-BTW: Does Oscar page with frequently asked questions in the documentation? |
+1 for allowing apps in the root directory - this is the default project layout for Django. Unless you consider oscar apps different from other apps - then you might want to namespace them. My project is mainly overriding various bits and pieces of oscar, so a flat project layout is fine. |
Fixed by #1718 |
Added usecase for oscar_fork_app command with dot path for forking to project_root dir. Added in django-oscar#1717
Documentation updating for #1717
Hello.
When im trying to fork some app to current dirrectory with blank
folder_path
argument i get aCommandError
exception from../oscar/management/commands/oscar_fork_app.py
with error:While im try to fork with dot (like a
./manage.py oscar_fork_app promotions .
) in__init__.py
file andconfig.py
file i got a invalid path.Now I am preparing to fix this error.
Please specify, how can do it in right way?
--edit--
I did commit that solves the problem, what do I do next?
p.s.it's my first time contributing, forgive my possible retarding :)
The text was updated successfully, but these errors were encountered: