We don't need it anymore, it was required when MFE was pushing the block to course. Now it only sends a message with selection details. I'll update it.
Thanks for the pull request, @bradenmacdonald!
### What's next?
*Please work through the following steps to get your changes ready for engineering review:*
#### :radio_button: Get product approv...
Thanks for the pull request, @bradenmacdonald!
### What's next?
*Please work through the following steps to get your changes ready for engineering review:*
#### :radio_button: Get product approv...
## Description
This implements a minimal UI so that [the WIP Problem Bank XBlock](https://github.com/openedx/edx-platform/pull/35553) is usable:
https://github.com/user-attachments/assets/093...
Like this: https://github.com/open-craft/edx-platform/commit/5939b5dada9f44f854d11dbe31ebef313349096a
Turns out this is actually necessary or sometimes a random message will come in and use up t...
@navinkarkera Oh, actually one more important thing: can you make sure this new button is only enabled if [`libraries_v2_enabled()`](https://github.com/openedx/edx-platform/blob/83827a3dc2794a70399...
Nit: you don't have to check _all_ the fields of `doc` again here. You can just check `doc["display_name"]`, `doc["description"]`, and `doc["published"]`
Thanks, this is great! I tested and it's working well.
Just one request: can you please add `published.display_name` and `published.description` to `update_searchable_attributes` in `edx-platfor...
Thanks, this is great! I tested and it's working well.
Just one request: can you please add `published.display_name` and `published.description` to `update_searchable_attributes` in `edx-platfor...
Also if you use an arrow function
```js
window.addEventListener("message", (event) => {
```
then you can remove the `.bind(this)` as it won't be necessary.
This can be fixed in a fast-follow PR if you want, but it's not a great UX that the "Next" button is sometimes hidden until you scroll, and the Next + Cancel buttons are in totally different places...
```suggestion
# Set `created_block.upstream` and then sync this with the upstream (library) version.
```
Why do we care about "preserving the former value of `created_block.upstream`...
I also have a draft "published" filter but it turns out to need some backend changes to implement and I haven't had time. CC @ChrisChV . https://github.com/openedx/frontend-app-authoring/pull/1406
> It seems like upstream sync will only [support blocks that were published](https://github.com/open-craft/edx-platform/blob/0da35c128f156f99e4ae1d8865fd888c0f95a9cc/cms/lib/xblock/upstream_sync.py...