chore: Bump the version of optimizely-sdk #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mfarhan943
force-pushed
the
mfarhan/bump-optimizely-sdk-version-34103
branch
2 times, most recently
from
fb6e563 to
11f1034
Compare
mfarhan943
force-pushed
the
mfarhan/bump-optimizely-sdk-version-34103
branch
4 times, most recently
from
93bf539 to
fe3f50e
Compare
* fix: pin urllib3 in user_retirement scripts
…penedx#35681) Adds a new Studio-only libraries static asset endpoint at /library_assets/blocks/{usage_key}. This endpoint will serve assets only from the Draft branch, and is only available to people who have read permission to the containing library. This also moves the existing library asset endpoint that did lookups by Component Version to /library_assets/component_versions/{uuid} This change was motivated by the desire to make it easier to make the editor preview work for images by having a single URL that will consistently point to the latest version of the asset, rather than having a new URL after every save (which the Component Version lookup
This is a new XBlock that presents a random subset of its children. As of this commit, the block can only be added as an Advanced component. For Sumac, we plan to enable it as part of the Libraries Relaunch Beta, under the name "Problem Bank (Beta)" The block does not care if its children are from V1 library, V2 library, or the course itself. It shares the randomization logic with LegacyLibraryContentBlock. It is also fully backwards-compatible with LegacyLibraryContentBlock. So, once V1 libraries are migrated to V2 libraries (after Teak), we eventually could point the `library_content` entry point at ItemBankBlock. Part of: openedx/frontend-app-authoring#1385
"Bare Bones" UI for Problem Bank [FC-0062] Part of: openedx/frontend-app-authoring#1385
This implements basic multi-select for adding components to a problem bank, for the Libraries Relaunch Beta [FC-0062]. Part of: openedx/frontend-app-authoring#1385
openedx#35707) We have user-oriented messaging stuffed into the BadUpstream exception. We may as well use it rather than just giving an opaque error about xblock references. We also want to log this situation, since we'd expect that the library block usage key that Studio provides should generally be valid. If it consistently isn't, then that's an issue that operators are going to want to look into.
Adds Problem Bank to the main New Components buttons. For the Libraries Relaunch Beta [FC-0062] Part of: openedx/frontend-app-authoring#1415 Co-authored-by: Jillian Vogel <[email protected]>
…openedx#35668) The biggest challenge is dealing with the mismatch between how Libraries store assets (per-Component) and how Courses store assets (global Files and Uploads space). To bridge this, we're going to kludge a component-local namespace in Files and Uploads by making use of the obscure feature that you can create folders there at an API level, even if no such UI exists. In this commit: * Assets work when copy-pasting between library components. * Assets work when copy-pasting from a library to a course, with the convention being to put that file in a subdirectory of the form: components/{block_type}/{block_id}/file. Note that the Studio course Files page still just shows the filename. * Assets work when copy-pasting from a course to a library. Top level assets are put into a static folder in the Component, per Learning Core conventions. Limitations: * Roundtrips don't work properly. * There's no normalized form, so directories will start nesting if you copy from library and paste into course, then copy the pasted thing and paste back into library, etc. This was deemed acceptable for Sumac. Low level stuff: * XBlockSerializerForLearningCore has been removed, with the url_name stripping functionality added as an optional param to XBlockSerializer (the other stuff was for children and "vertical" -> "unit" conversion, neither of which are relevant now). * url_name is now stripped out of anything added to the clipboard, so that we don't end up writing it in block.xml when it is redundant (and would be stripped out with the next write anyway). For the Libraries Relaunch Beta. This should not affect any site which has kept New Libraries disabled. Issue: openedx/frontend-app-authoring#1170
mfarhan943
force-pushed
the
mfarhan/bump-optimizely-sdk-version-34103
branch
from
fe3f50e to
3bb77e8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Describe what this pull request changes, and why. Include implications for people using this change.
Design decisions and their rationales should be documented in the repo (docstring / ADR), per
OEP-19, and can be
linked here.
Useful information to include:
"Developer", and "Operator".
changes.
Supporting information
Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.
Testing instructions
Please provide detailed step-by-step instructions for testing this change.
Deadline
"None" if there's no rush, or provide a specific date or event (and reason) if there is one.
Other information
Include anything else that will help reviewers and consumers understand the change.