Skip to content
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

Content libraries paging #9

Closed

Conversation

e-kolpakov
Copy link

No description provided.

@e-kolpakov
Copy link
Author

container_spec.js seem heavily modified, but in reality I just wrapped entire test suite in parameterized_suite function and called it with parameters for paged and non-paged container view. There are some minor changes to allow for it, though.

</script>
% endfor

<div class="xblock-container-paging-parameters" data-start="${first_displayed}" data-displayed="${displayed_children}" data-total="${total_children}"/>
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like the idea of passing data through data attributes in rendered html, but it's a workaround that allows paging to work. Otherwise some invasive modifications need to be made to the way child XBlocks are delivered to studio

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I see what you mean. The only thing I can suggest for now is changing the end of this line slightly since <div /> is not valid HTML5.

@bradenmacdonald
Copy link
Member

Very nice work @e-kolpakov! Seems to work very well. Comments made inline.

The only issue I encountered is just missing functionality: right now if I go to page 3 then refresh, I find myself back on page 1. I think you should use history.pushState() so that the "current page" is represented in the URL (and also fix the page links to preventDefault() so # isn't added to the URL when they are clicked). I know that may be complicated to implement though so maybe you want to make that a future sprint task or wait until upstream has signed off on this.

As for how you chose to implement this overall, I think it's good, but we'll have to see what upstream says :)

@e-kolpakov
Copy link
Author

@bradenmacdonald thanks for the review! I've addressed those inline review notes. As of history - unfortunately there are no Backbone routing present at where we are, so we either need to implement backbone routing or do history manipulations using plain HTML5 API.

I've spent about an hour implementing HTML5 version. In the end it was capable of tracking history and handling back button, but with bugs and zero test coverage. So I decided that it deserves a separate task.

@bradenmacdonald
Copy link
Member

@e-kolpakov Sounds good :)

@bradenmacdonald
Copy link
Member

This will need to be rebased onto content_libraries/2-studio-lib-support. The rebase will be complicated by the fact that I changed the library XModule to a pure XBlock, but although that will be a conflict it should make the code nicer and simpler in the end. This branch will also need bok choy tests.

Once PR 6046 has been merged, we will open an upstream PR to merge this branch into the content-libraries feature branch.

@e-kolpakov
Copy link
Author

@bradenmacdonald just one question is content_libraries/2-studio-lib-support ready for rebasing? I mean, since it's a base for PR 6046, there will be more modifications to it while you address the comments from upstream review, so it might make sense to hold off rebasing this branch until PR 6046 is merged, to reduce the number of rebases.

@bradenmacdonald
Copy link
Member

@e-kolpakov Yes, you might want to wait until PR 6046 is merged. Up to you.

@e-kolpakov e-kolpakov deleted the content-libraries-paging branch January 8, 2015 08:33
e-kolpakov pushed a commit that referenced this pull request Apr 14, 2015
Story #4: Coaches sees grades.

Story #9: Coach downloads grades.
pomegranited pushed a commit that referenced this pull request Oct 3, 2018
* Adds actual number of assignments types assigned to.
* Adds total weight validation on assignment types.
* Adds Assignment type weight summary modal dialog.
* Adds translated strings (he, ar)
lgp171188 pushed a commit that referenced this pull request Mar 15, 2019
…em-nltk

Install chem nltk from edX fork, and fix django-wiki dependency. Rue89

(cherry picked from commit e3297b4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants