-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feat: implement --verbose flag on ion template inspect
cmd
#21
Conversation
This commit should fully resolve issue: #9 (comment) |
modified grcov action by commenting out `actions-rs/install` - as the doc comment suggests
remove rust-flags which are causing compilation of Ion-derive to fail building
thanks, I'm trying to add codecov to the CI so probably need to wait for me a bit on fixing the CI before merging this PR then we will have a code coverage report on the unit tests. |
The CI should be fixed now, could you merge |
Working on it now - just be a few minutes... |
Codecov ReportBase: 55.24% // Head: 55.45% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #21 +/- ##
==========================================
+ Coverage 55.24% 55.45% +0.21%
==========================================
Files 74 74
Lines 4502 4526 +24
==========================================
+ Hits 2487 2510 +23
- Misses 2015 2016 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@@ -15,12 +15,291 @@ Download tarball in the release page and extract it to your `$HOME/.julia` direc | |||
|
|||
### build from source |
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.
it'd be nice if this can be in a separate PR, I probably will put up the website soon, so we can decide whether to have this in a different PR
src/ion/blueprints/template.rs
Outdated
@@ -22,3 +24,80 @@ pub struct Template { | |||
pub coveralls: Option<Coveralls>, | |||
pub github: Option<GitHub>, | |||
} | |||
|
|||
impl fmt::Display for Template { |
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.
this should be in derive macro for Template, so things can be kept extensible
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.
Thanks for the help!
The latest commit should resolve these issues, I believe.
ion_derive/src/template.rs
Outdated
self.name, self.description | ||
)?; | ||
|
||
if let Some(repo) = &self.repo { |
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.
you need to generate the names instead of manually writing them, like how I generate other methods
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.
this one might take a little while -- I have zero experience writing Rust macros (I know how to use them, just not how to write them).
But I'm reading up on it. The resources are a little thin, but I'll get it eventually...
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.
Yeah, perhaps we should just do the debug printing, so that you don't need to implement this now
actually, why don't we just use the debug print? It seems you are implementing something similar anyway? |
If you prefer the debug print output, I can certainly do it that way. However, I did actually try the straight debug print option first, before the current implementation, and found that I didn't have enough context to understand what that debug output actually meant. I realize that improvements to the display output could be made -- maybe printing out the info in tabular form would be better, or something like that? -- I just don't have enough experience with the templating sub-system right now to be able to design a better output. That's one of the reasons I listed some issues on the templates repo: I think once I make 1 or 2 of my own templates, I think I'll have a better handle on what needs to be displayed to make the output truly informative for future users. Then I can come back around and redesign this output (or at least add color / additional structure). Thoughts? Would you prefer just to do the debug output right now? Or are there other recommendations you have for improving the intelligibility of the output? Thx. |
Yeah I think maybe let's just do the debug print for now since it's way more simpler and also verbose enough, especially it doesn't require us changing the procedure macro, we can think better printings in the future. |
So, I've changed to debug printing as requested, though I've left the basic code for re-implementing the Display trait on the Template and all its related sub-structs in place if we want to customize in the future. |
The impl Display stubs have been removed. |
Yeah I think current one looks pretty good to me! Thanks! |
I had a little extra time over the last couple of days, so I thought I'd finish this off.
I also included an update to the README / docs, just to flesh it out a bit until you have the time to fill out the Readme a little more with your own words.