-
Notifications
You must be signed in to change notification settings - Fork 40
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
TypeError: Invalid path type: tuple #83
Comments
Hi @Moiez789, thanks for letting us know that you're having an issue related to paths. The issue where you added your comment is now closed since it's been resolved. I'm moving your comment to a new issue. I'm happy to help but in order to assist, I'll need much more detailed information to understand exactly where this problem is occurring and to investigate whether it's actually a bug in django-drf-filepond or whether you're passing some incorrectly formatted/structured data, in which case some improvement or clarification to the documentation may be useful. Can you please let me know:
Normally, by far the easiest way to investigate and solve these problems is to produce a minimal example that triggers the error, i.e. can you cut out anything specific to your application and provide a few lines of code offering a simple example that triggers the error - then a maintainer can much more easily investigate and try to reproduce the problem. They can then help you solve the problem, or fix something if there's a bug in the library you're trying to use. |
There was not enough information in the original issue report - it's unclear when the reported error TypeError: Invalid path type: tuple is coming from django-drf-filepond or another element of the app in which this library is being used. Without any further detail such as the file and line in which the error is being reported, it's not possible to investigate this further. Since there was no follow-up to the above request for further information, this is being closed. If anyone else experiences this issue and is able to provide further detail, feel free to repoen this issue with additional information. |
Originally posted by @Moiez789 in #49 (comment)
Opening a new issue for this since the original location has been closed.
The text was updated successfully, but these errors were encountered: