-
Notifications
You must be signed in to change notification settings - Fork 71
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
feat: replace rest_framework_swagger with drf_yasg #1502
Conversation
Thanks for the pull request, @NeOneSoft! I've created OSPR-6284 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
credentials/urls.py
Outdated
urlpatterns = oauth2_urlpatterns + [ | ||
re_path(r"^admin/", admin.site.urls), | ||
re_path(r"^api/", include(("credentials.apps.api.urls", "api"), namespace="api")), | ||
re_path(r"^api-auth/", include((oauth2_urlpatterns, "rest_framework"), namespace="rest_framework")), | ||
re_path(r"^api-docs/", get_swagger_view(title="Credentials API"), name="api_docs"), | ||
re_path(r"^api-docs/$", schema_view.with_ui('swagger', cache_timeout=0), name="api_docs"),, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@NeOneSoft Looks like we may have an extra comma here that is causing issues the config files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@justinhynes Thank you so much!!!
2792b87
to
5f2d5ca
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@NeOneSoft I think we're really close getting this PR wrapped up. It looks like we're running into a few quality issues. We should be able to use our existing tools to automate the fixes. Locally you can try running:
make isort
- this should fix the error with the imports in the wrong order, then
black .
- (note the period) black is a code formatter used in this repo to keep syntax common across all files.
From there you can run make quality
locally to have isort/black/pylint run to point out any other potential quality issues.
I think after this we should be good to squash and merge the changes. :)
@justinhynes !!!!Thank you so much for you instructions and support. I already apply the suggested commands and once our quality issues were checked I will be doing squash!! |
Hey@justinhynes!! after apply isort, black and quality we're still having and import issue on copy_catalog.py file but I think that the sort is correct. |
@NeOneSoft I'm sorry this is such a pain in the neck! I definitely didn't expect 126 files to be updated. I'm curious as to what is going on here. Going to take some extra time to think this through... thanks for your patience. |
No problem @justinhynes!!!!I'll be attending your comments, thanks again for all your support!! |
@NeOneSoft Hey there! Apologies that I haven't been able to return and triage your issues any further. I am wrapping up my day here soon and actually am off until January. If it's okay with you, we can try and get this sorted out shortly after the new year. Thanks for understanding and talk soon! |
Thank you so much @justinhynes, enjoy and happy holidays!!!! |
@NeOneSoft Thanks so much for your contribution. @justinhynes Thank you for reviewing! |
Hey @NeOneSoft, I'd like to get this merged but I think we will need to reduce the number of touched files. Are you able to rebase and do some commit cleanup? I would like to see 5f2d5ca fixed up to the commit before it (just in case we end up dividing up this PR, I don't want that fixup to be separated from the commit it fixes) and then pull out 93db679 for the time being. You could stash it in another branch for now, and then we can determine if we want to pull some of it in piecemeal. Does that sound doable? |
Hi @hurtstotouchfire , thanks for your review I think that in the last fix I touched many files so I'll do you the cleanup for this as you mentioned to move forward. |
@NeOneSoft Please let us know once you are ready for this to be reviewed again. |
Hi @natabene of course, I'll be working on it this week! |
Hi @hurtstotouchfire!!,Are you agree if I store the changes of 94db679in another branch as you suggested and then I reset and squash to 5f25ca?Thanks in advance |
d15c1f0
to
5f2d5ca
Compare
feat: modify settings base.py and url.py files feat: remove an extra comma from urls.py file feat: resolve conflicted files feat: resolve remaining conflicted files feat: resolve conflicted files and requirment versions
4fc504a
to
49c8f0d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as @justinhynes has no blocking concerns I think this is good to go from our perspective. I think you may need to resolve conflicts though.
Hey @NeOneSoft, I was taking another look at this and I think I found one final complaint. It looks like you did the right steps to add Please run Otherwise, if we were to merge this, the service won't come up successfully as the So, to summarize:
Afterwards, as long as all the tests pass, we should be good to go! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The drf_yasg
package is missing from the base.txt
file and will cause an issue if not included. Please see my latest comment on your PR to fix this issue. Thanks!
Hi @justinhynes !!Thanks a lot for your review. I already run the commands are you suggested. I'll be glad to attend your comments and thanks again |
@NeOneSoft Great, thank you for those changes. I took a look and it looks good to go. I'm going to approve the PR. |
🎉 |
Hmmmm we have merge conflicts again. Sorry @NeOneSoft this tends to happen when there are dependency updates because we are also merging update PRs so they tend to conflict. |
No worries @hurtstotouchfire !!!, should we wait to get updated all our dependencies before apply make upgrade again? |
@NeOneSoft I had one more update PR to merge which may or may not conflict for you but after this you should be good to go. This is the PR: #1689 Let us know when you're de-conflicted! |
Hi @hurtstotouchfire!!, I had errors rebasing this branch so I created a new one on PR with exactly the same changes but starting from updated master. I think that this should be solve the conflicts. For last, could you please review it to be sure that everything it's ok?. For know titled as "draft" but I will change it once this is ready for merge. Thanks a lot !! |
This PR can be closed on behalf of PR where the required changes were done and some issues regarding python 3.8 dependencies where solved. Thanks everyone for your all your support!!!! |
@NeOneSoft Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future. |
This PR was created following edx/upgrades#17 to switch django rest swagger to drf-yasg