Skip to content
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

More edit "friendly" choco new nuspec template creation for non-beginners #1366

Closed
bcurran3 opened this issue Jul 19, 2017 · 9 comments
Closed

Comments

@bcurran3
Copy link

In the spirit of https://github.com/chocolatey/choco/issues/1303...

The default nuspec template created by choco new is a big pet peeve of mine. It consists of very useful information for new packagers stepping through it, but it's a big pain in the keister to edit/remove so much of the tutorial info and replace it with the actual package's needed info.

I brought this topic up and provided a submission for a different format here. Unfortunately it didn't gain much traction. So now it's a feature request! :)

I don't care if my example gets used or not. What I'd like to see is the default template created by choco new become "edit friendly." By this I mean that all instructions and help get commented above or below the element tag and the element tag is left alone to be filled in without having having to hit the backspace 50 times and then retyping in the ">." :)

As a new alternative, and I'm starting to like this idea even better, is have the top of the file be a blank template ready to fill in. This top part has nothing that needs to be edited out or changed at all. (No damn select and cut! No damn backspacing!) The template would be ready to start accepting pasted in information. Below that, could be one big huge commented out section which has a general overview followed by specific elemental tag details and possibly an example for each.

In my first suggestion, the pro is that it's easier to edit and the reference information is where you need it. The con is that the packager needs to edit out multiple portions to clean up the file (but MUCH easier than the amount of editing out as it's presented now).

In the latter suggestion, the pro is that it's faster for packagers that remember what the elements are to enter the information quickly and it's only one quick select and cut to clean up the file. The con is that packagers less familiar with the information they need to enter will be scrolling up and down a lot.

Either way. --->IMHO<--- the generated file really needs to be more "edit friendly."

@bcurran3
Copy link
Author

bcurran3 commented Jul 30, 2017

No Enhancement tag yet? :)
I'm a Pro user, does this qualify for a Customer tag? :)

(Yay - I've got Kim's backing!)

Another alternative would be to generate a ready to edit template file with NO COMMENTS and a separate help file for the template.

@ferventcoder ferventcoder changed the title FEATURE REQUEST: More "friendly" choco new nuspec template creation - easier to edit. More edit "friendly" choco new nuspec template creation for non-beginners Aug 6, 2017
@ferventcoder
Copy link
Member

You know you can create your own templates right? 👍

@ferventcoder
Copy link
Member

I'm a Pro user, does this qualify for a Customer tag? :)

It could, but those are typically found with bugs or high priority things. This has a fantastic documented way of doing this now, that let's folks customize new package creation just for them. Everyone is going to have a different preference so we optimize the default template for new packagers.

@bcurran3
Copy link
Author

bcurran3 commented Aug 7, 2017

You know you can create your own templates right? 👍

I do! 👍 I have a custom default for generation and at least 8 specific ones, BUT this is still a big pet peeve for me even though I don't use the default one any more. :)

This has a fantastic documented way of doing this now, that let's folks customize new package creation just for them.

I find it far from fantastic! Sorry, feel strongly about this. I absolutely hate it. I understand everyone has an opinion, mine is simple: split the documentation and the nuspec into two separate areas so that it's easier read and edit.

Low priority or not, thanks for putting it on the roadmap - I think it will be a helpful change.

@ferventcoder
Copy link
Member

@bcurran3 you can also replace the default template so you don't need to pass template name, just put one into the templates folder named "default".

@bcurran3
Copy link
Author

@bcurran3 you can also replace the default template so you don't need to pass template name, just put one into the templates folder named "default".

I do! 👍 I have a custom default for generation and at least 8 specific ones, BUT this is still a big pet peeve for me even though I don't use the default one any more. :)

I'm still a big fan of the concept of having an easily editable base choco new template with no comments anywhere near the actual edit fields and then having a completely separate "tutorial" section at the bottom.

I'm not sure what is actually set as the milestone, but people who like my concept (or not) please VOTE!

@ferventcoder ferventcoder modified the milestones: 0.10.13, 0.10.14, 0.10.15 Mar 9, 2019
@ferventcoder ferventcoder modified the milestones: 0.10.15, 0.10.16 Apr 1, 2019
@gep13 gep13 modified the milestones: 0.10.16, 0.10.17 May 31, 2019
@ferventcoder ferventcoder modified the milestones: 0.10.17, 0.10.18 Jan 14, 2020
@ferventcoder ferventcoder modified the milestones: 0.10.18, 0.10.x Apr 14, 2021
@TheCakeIsNaOH
Copy link
Member

TheCakeIsNaOH commented Sep 22, 2021

I've been playing around with ideas for this. I'm thinking it might be better to have two built in templates. The current default one, and the one suggested in this issue. Perhaps they could be called standard and slim?

@TheCakeIsNaOH
Copy link
Member

After discussion with @gep13, this is something that should be added to the community templates instead of directly into choco.
chocolatey-community/chocolatey-templates#15

@TheCakeIsNaOH
Copy link
Member

As mentioned in the comment above, it will be added as an installable template.

@TheCakeIsNaOH TheCakeIsNaOH closed this as not planned Won't fix, can't repro, duplicate, stale Jul 30, 2022
@TheCakeIsNaOH TheCakeIsNaOH removed this from the Future milestone Jul 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants