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

Fix forked component state #358

Merged
merged 2 commits into from
Sep 8, 2023

Conversation

shelegdmitriy
Copy link
Contributor

Closes #348

@vercel
Copy link

vercel bot commented Sep 6, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
near-discovery ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 8, 2023 1:40pm
near-discovery-testnet ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 8, 2023 1:40pm

@calebjacob
Copy link
Collaborator

I'm not super familiar with the sandbox editor code, so I'll let @marcinbodnar be the one to approve this one. :)

Copy link
Contributor

@marcinbodnar marcinbodnar left a comment

Choose a reason for hiding this comment

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

@shelegdmitriy It seems like it doesn't solve the problem, try refreshing the page.

I can take this issue from you, it's a bit problematic, and I think I was fixing the same issue a few months ago.

@shelegdmitriy
Copy link
Contributor Author

I actually tried and it was working

@shelegdmitriy
Copy link
Contributor Author

Have you tried to run my branch locally?

@marcinbodnar
Copy link
Contributor

@shelegdmitriy I tried on the preview.

@shelegdmitriy
Copy link
Contributor Author

@marcinbodnar I did the same on preview and I can't reproduce this anymore

@@ -440,7 +424,9 @@ export const Sandbox = ({ onboarding = false }) => {
selectFile(newPath);
};

// possibly unused
Copy link
Contributor Author

Choose a reason for hiding this comment

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

It seems this section below is unused @marcinbodnar could you confirm that?

@calebjacob
Copy link
Collaborator

@shelegdmitriy Both preview links seem to work for me.

@marcinbodnar marcinbodnar self-requested a review September 8, 2023 16:55
Copy link
Contributor

@marcinbodnar marcinbodnar left a comment

Choose a reason for hiding this comment

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

There is an issue with the red dot that indicates if there are any changes made to the component. It doesn't disappear after you undo the changes made.

We can merge it but the issue should be addressed in a separate PR cc @charleslavon

The main issue is resolved and works well.

@shelegdmitriy
Copy link
Contributor Author

@marcinbodnar good catch! That should be fixed for sure but in a separate PR because it's very minor issue

@shelegdmitriy shelegdmitriy merged commit ba30720 into develop Sep 8, 2023
3 checks passed
@shelegdmitriy shelegdmitriy deleted the fix/forked-component-local-storage branch September 8, 2023 17:06
charleslavon pushed a commit that referenced this pull request Sep 28, 2023
* Fix forked component state

* Second attemp to fix bug
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.

[BUG] Forked component changes do not persist in LS
3 participants