-
Notifications
You must be signed in to change notification settings - Fork 47
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
Printing a campaign object can be overly verbose when using chemical descriptors #96
Comments
Hey Sterling, Fixing this is already on our feature-wishlist / roadmap. One of the issues were facing is that we have an "old" set of workitems in Azure Devops project management (not public). Compared to that, Github project and work item management is surprisingly terrible, this is why we havent moved it anywhere where it is publicly visible yet. Not sure how to fix that, any suggestions? |
@sgbaird I just wanted to inform you that we started to implement "pretty printing" functionalities. Once we have implemented the first ones, we will inform you here. |
closing, as this has been resolved with #124 |
@Scienfitz This is technically not yet completed: Although we have implemented pretty printing for search spaces via #124 , pretty printing for the full |
@AVHopp which parts of Campaign can now cause an overly verbose print? |
The |
@AVHopp this issue is about overly verbose campaign print and not about having everything pretty printed. So if the excessive verbosity has been resolved already with the searchspace pretty print, this issue is closed, if not it should be reopened |
@Scienfitz Currently, pretty printing of the search space is not yet shown in the campaign, hence this issue is still open. |
@Scienfitz exactly. The idea was to first have PRs for the individual subparts of a campaign and then have one "final" PR using all of the pretty printed objects within the campaign. |
@AVHopp imo theres no need to wait for pretty print of all other objects and the new functionality should simply be added to campaign first as it would solve this issue, then further pretty prints can follow, if you already reference the |
This will be implemented asap then. |
By now, this is included, so this issue can be closed. |
Maybe this is intended, but here is an example of the
campaign
object from the README:The text was updated successfully, but these errors were encountered: