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

feat: show alert while editing v2 library content [FC-0062] #35700

Merged
merged 9 commits into from
Oct 23, 2024

Conversation

navinkarkera
Copy link
Contributor

@navinkarkera navinkarkera commented Oct 22, 2024

Description

Adds warning alert in edit modal for library v2 content in both legacy and new mfe editors.

Legacy

FAL-3877-recording.mp4

New MFE editors:

vokoscreenNG-2024-10-23_12-30-33.mp4

For openedx/frontend-app-authoring#1340

Supporting information

Testing instructions

Follow instructions in openedx/frontend-app-authoring#1392

Deadline

Today

@openedx-webhooks
Copy link

openedx-webhooks commented Oct 22, 2024

Thanks for the pull request, @navinkarkera!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/wg-maintenance-edx-platform. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Oct 22, 2024
@navinkarkera navinkarkera marked this pull request as ready for review October 22, 2024 15:34
@navinkarkera navinkarkera force-pushed the navin/upstream-warning-alert branch 2 times, most recently from 20c34d6 to 53bb6c3 Compare October 22, 2024 16:41
@bradenmacdonald
Copy link
Contributor

I think this PR will need to be re-worked. We don't need any UI changes on the platform side; we just need it to pass some parameter like ?showLibraryWarning in the URL when opening the MFE editor for any block that has an upstream set.

Then, in the MFE editor code in frontend-app-authoring, we can display the warning when that query string is present.

Copy link
Contributor

@ChrisChV ChrisChV left a comment

Choose a reason for hiding this comment

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

Looks good 👍

  • I tested this: I followed the testing instructions
  • I read through the code and considered the security, stability and performance implications of the changes.
  • I tested that the UI can be used with a keyboard only (tab order, keyboard controls).
  • Includes tests for bugfixes and/or features added.
  • Includes documentation
  • Includes fixtures that create objects required for manual testing.

@mphilbrick211 mphilbrick211 added the FC Relates to an Axim Funded Contribution project label Oct 22, 2024
@navinkarkera navinkarkera force-pushed the navin/upstream-warning-alert branch from 53bb6c3 to e8da227 Compare October 23, 2024 06:24
@navinkarkera
Copy link
Contributor Author

navinkarkera commented Oct 23, 2024

@bradenmacdonald @ChrisChV Updated this and frontend PR to display warning in both legacy and new editors when editing content imported from library.

Edit: The warning is not displayed for new xblocks that are added via library content option. Currently, the mfe editor is opened as soon as the new block is imported and there we cannot see the alert. I think we should not display editor as soon as new block is imported.

Update: This commit: 7afe528 makes it such that new editors are not displayed by default on importing blocks from library.

Copy link
Contributor

@ChrisChV ChrisChV left a comment

Choose a reason for hiding this comment

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

Looks good 👍

@bradenmacdonald
Copy link
Contributor

I think we should not display editor as soon as new block is imported.

Update: This commit: 7afe528 makes it such that new editors are not displayed by default on importing blocks from library.

Thank you, that was a very annoying bug.

Copy link
Member

@kdmccormick kdmccormick left a comment

Choose a reason for hiding this comment

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

I locally rebased & tested this. The margins/padding feel a little wonky, but functionally, it's great!
image

I have some refactoring requests, which I'll leave in a separate review. Don't worry about them for today-- we can apply them in a follow-up after the Sumac cut.

@bradenmacdonald
Copy link
Contributor

@kdmccormick Hmm, it should look nicer than that - see video at openedx/frontend-app-authoring#1392 Maybe your CSS is not updated?
BTW that PR should merge before this one, but it looks like they're both ready.

@navinkarkera
Copy link
Contributor Author

@kdmccormick It looks like the scss changes has not been applied in the image. Can you try hard reload and/or run npm run watch in cms shell.

@ChrisChV ChrisChV enabled auto-merge (squash) October 23, 2024 15:26
@ChrisChV
Copy link
Contributor

Update: I think it's ready to merge, I enabled the auto-merge.

@kdmccormick
Copy link
Member

Yup, my CSS was just outdated 👍🏻
image

@kdmccormick
Copy link
Member

kdmccormick commented Oct 23, 2024

@ChrisChV Can you make sure your squashed commit is a single cohesive message with a ticket link, minus the intermediate style:, fix:, etc. commit messages?

For example, like 4158a44 or d25e651

EDIT: I did it myself

@kdmccormick kdmccormick disabled auto-merge October 23, 2024 15:55
@kdmccormick kdmccormick enabled auto-merge (squash) October 23, 2024 15:56
@kdmccormick kdmccormick merged commit e2a9a37 into openedx:master Oct 23, 2024
48 checks passed
@ChrisChV
Copy link
Contributor

Can you make sure your squashed commit is a single cohesive message with a ticket link, minus the intermediate style:, fix:, etc. commit messages?

Sure, thanks for the suggestion!

@bradenmacdonald bradenmacdonald deleted the navin/upstream-warning-alert branch October 23, 2024 16:15
@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

1 similar comment
@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FC Relates to an Axim Funded Contribution project open-source-contribution PR author is not from Axim or 2U
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

7 participants