-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Add output selection support for ethdebug #15293
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I was wondering if it would also be an option to throw in case the output is requested (together with the appropriate debug-info
flag) as you're essentially just swallowing it now which might confuse someone unsuspecting. But then again it's not listed in the options so I think it's fine this way as well.
I will still add the standard-json import part to this PR. This part I didn't pushed yet, because I saw that I need to add additional tests to verify validation logic. I will add this later today. |
@@ -995,6 996,8 @@ void CommandLineInterface::handleCombinedJSON() | |||
contractData[g_strFunDebugRuntime] = StandardCompiler::formatFunctionDebugData( | |||
m_assemblyStack->runtimeObject(contractName).functionDebugData | |||
); | |||
if (m_options.compiler.combinedJsonRequests->ethdebug) | |||
contractData[g_strEthdebug] = Json::object(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Combined JSON has been deprecated for ages now (#10278) and we're likely to drop it in the next breaking release. It does not make sense add more things to it at this point.
This should be standalone compiler output instead.
5ef3239
to
77c474a
Compare
ec729b3
to
ee2bc12
Compare
ee2bc12
to
9772d20
Compare
Replaced by #15289. |
Depends on #15289.