-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Usage in App is not working because of namespace issues #89
Comments
Hi @peterbaumert, Thank you for reaching out. However, I am not 100% sure I fully understand the issue you are describing. What kind of exception are you seeing? Maybe include the actual exception message and stack trace. A bit of real life code, might also go a long way here. Anyhow, based on what I see, providing your own namespace, should not be needed. In fact, it may cause the error you are experiencing. The I hope this helps! Cheers, |
So if I just add the urls (where I also have
i get
|
So i checked a littel more, it does add the urls in the right app namespace, here "services:fileshareorderworkflow:details" |
Yes, that seems to be an issue. However, we don't have access to the resolver in the I see two options:
What do you think? Do you still care to provide a patch? |
i will have a look those days yes.
|
So I took some time to look into it. One issue is that Line 165 in 0906fb5
get_absolute_url() functions it needs to return the "app prefixed" string.
So I guess this needs to either be split in two functions or in that line above changed to What do you think? |
Wait, I don't think I get your point. Isn't this identical, since that's how Lines 178 to 180 in 0906fb5
|
https://github.com/codingjoe/joeflow/blob/8d58695eeee2502d731fb5dde2491dba63e28c09/joeflow/models.py#L177C29-L177C29
If I use joeflow in an app in my project, the method to get the url namespace returns a wrong resulst.
it should be something like
maybe somehow conditionally check if
cls._meta.app_label
existsadditionally one needs to specify the urls as follows:
The text was updated successfully, but these errors were encountered: