fix: clicking on back button after post creation

[DmytroAlipov]

Description

Steps to Reproduce:

1. Open course in LMS

2. Open discussions sidebar

3. Add post -> Submit
   

4. Click on back browser button
   

5. Result
   

Result of the investigation:

Found that post id is unpacked when saving to state, although it should be saved intact:

After fixing the unpacking, this error also started to occur:

I have added a check that the post exists to fix this situation:

[openedx-webhooks]

Thanks for the pull request, @DmytroAlipov!

This repository is currently maintained by @openedx/edx-infinity.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are 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.

---

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:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.18%. Comparing base (58aa512) to head (a17949f).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #745   +/-   ##
=======================================
  Coverage   93.17%   93.18%           
=======================================
  Files         161      161           
  Lines        3401     3402    +1     
  Branches      924      924           
=======================================
+ Hits         3169     3170    +1     
  Misses        214      214           
  Partials       18       18           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mphilbrick211]

Hi @openedx/2u-infinity! This is ready for review.

[mphilbrick211]

Hi @openedx/2u-infinity! This is ready for review.

Friendly ping on this @openedx/2u-infinity

[Copilot]

PR Overview

A bug fix to ensure that the correct post ID is retained and processed when clicking the browser back button after creating a post. Key changes include:

• Adding a null check for post objects before processing in the post list hook.
• Updating the merging logic for post IDs in the discussions slice to avoid unpacking errors.

Reviewed Changes

File	Description
src/discussions/posts/data/hooks.js	Adds a check for post existence before processing.
src/discussions/posts/data/slices.js	Updates array merging logic for post IDs.

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

The updatedPages[page - 1] array is not being spread into the set, which may lead to nested arrays and incorrect deduplication. Consider reverting to spreading the array as in the original code: [...new Set([...updatedPages[page - 1], ...ids])].

Suggested change

	updatedPages[page - 1] = [...new Set([updatedPages[page - 1], ...ids])];
	updatedPages[page - 1] = [...new Set([...updatedPages[page - 1], ...ids])];