-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error When Cloning ValueObject #152
Labels
Comments
4lessandrodev
added
bug
Something isn't working
good first issue
Good for newcomers
labels
May 1, 2024
4lessandrodev
added a commit
that referenced
this issue
May 2, 2024
4lessandrodev
added a commit
that referenced
this issue
May 2, 2024
4lessandrodev
added a commit
that referenced
this issue
May 2, 2024
4lessandrodev
added a commit
that referenced
this issue
May 2, 2024
4lessandrodev
added a commit
that referenced
this issue
May 2, 2024
4lessandrodev
added a commit
that referenced
this issue
May 2, 2024
4lessandrodev
added a commit
that referenced
this issue
May 2, 2024
This was referenced May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
When a ValueObject is cloned using the clone() method, the value of the cloned object is not properly maintained. When attempting to access the value using the get('value') method, the return is null instead of the original value.
Steps to Reproduce:
Expected Behavior:
The clone() method should create an exact copy of the ValueObject, keeping the original value intact. Therefore, when accessing the value using the get('value') method on the cloned instance (copy), the returned value should be the same as on the original instance (main).
Observed Behavior:
After cloning the ValueObject, the value returned when accessing get('value') on the cloned instance is null, instead of maintaining the original value.
Environment:
Language: TypeScript
Framework/Dependency: rich-domain (version v1.23.0)
Operating System: linux
Browser/Platform: nodejs v20
Sample Code:
The text was updated successfully, but these errors were encountered: