-
Notifications
You must be signed in to change notification settings - Fork 147
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
@original-name
doesn't include parent objects
#3728
Comments
@yegor256 may I try this one? |
@Suban05 sure, you can try! |
@yegor256 @maxonfjvipon Could you please explain how I can get this result
I've checked the file
|
@yegor256 it seems the attribute |
@maxonfjvipon it should be the FQN of EO object |
@yegor256 isn't |
@maxonfjvipon well, it has the same meaning, but it's not the same. It's better to keep the original name intact. It may help us in the future, to trace bugs. |
@Suban05 as you may see - your task came down to adding |
#3728 add `@original-name` attribute including parent objects
In
.xmir
files, for example ingo.xmir
that stays in theeo-runtime/target/eo/8-transpile/org/eolang/
directory, there is this object:Obviously, the
@original-name
is set wrong. Should be:go.to.token.jump
, while it hasjust
jump
.When this is fixed, let's fix
Dataized
too: it must not log errors iforg.eolang.go.to.token.jump
is encapsulated in the instance ofEOerror.ExError
that is caught.The text was updated successfully, but these errors were encountered: