-
-
Notifications
You must be signed in to change notification settings - Fork 956
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
SAK-50500 LTI rename basiclti to lti #12902
Conversation
I checked this out and it looks like it runs as expected. There are still a lot of "BASICLTI" references in the code which we might cleanup on a separate issue after this is merged rather than trying to fix it all here. Of these I think only 1 needs to be updated, but that's easy. 2 would be nice to have. 3 sounds like a large project.
(This might be a separate issue) Lessons has
But that should be |
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.
I'll approve this as it looks like it works as it is. These changes I suggested could be done here or in another issue/pr.
@jonespm Thanks for the review. I will definitely do 1 and 2. Issue 3 is very much on purpose and would be another much later JIRA - I wanted to avoid any DB conversion on this JIRA. I don't want to fix 4 in this JIRA - lets make it another JIRA - the switch in IMS world makes things a little trickier and needs to be thought of as not just a "rename" in our code. |
this should not be merged until #12843 has been merged |
This is two commits to make sure that git does not get confused w.r.t. the renames and text changes in a single commit. So don't squash these when merging to give us the best chance of tracking chances across the name changes.
You might find it easier to review the two commits separately. The second commit is all file changes - they first commit is merely renames in order to give us the best chance at history carryover.
This branch is running on dev1.sakaicloud.com is you want to test it on an actual system - this is the partner test server so clean up after yourself and don't break any one else's test setups.
This is aimed at Sakai 25.0. We will not merge this into master until we have done some testing on the branch. The target for merging this is 24-Sep-2024.