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

Set value refactoring #105

Open
wants to merge 26 commits into
base: main
Choose a base branch
from
Open

Conversation

nerzhulart
Copy link
Contributor

@nerzhulart nerzhulart commented Mar 16, 2017

This PR fixes the issues with SetValue:
SetValue now throws special exception (ValueModificationException) to be shown to user in frienly way. Before in the most of cases it failed silently without any errors.
NOTE: #85 has to be merged first, because this change is dependent on that
See commits starting from da12417

… for many times. Maybe this may help to avoid hanging evaluations. (Moved from MD repo)
@nerzhulart nerzhulart force-pushed the setValueRefactoring branch from 94b6322 to 6e14dfe Compare March 16, 2017 20:32
nerzhulart and others added 10 commits March 17, 2017 16:13
…modification is failed instead of supressing the exception. This allows to show the error info to user at the call site (e.g. in message box).

ValueReference.SetValue() and ArrayElementGroup.SetValue() implementations unified and moved to ValueModificationUtil.

(cherry picked from commit 316b7cc)
Documentation updated.

(cherry picked from commit fdffbaa)
…shown in watch view

(cherry picked from commit abcd933)
(cherry picked from commit 2e51f2e)
@nerzhulart nerzhulart force-pushed the setValueRefactoring branch from 6e14dfe to e6f8fb0 Compare March 17, 2017 16:52
Base automatically changed from master to main March 4, 2021 12:37
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.

1 participant