Using and Mastering Cookiecutter Transcripts
Chapter: Adding features to Cookiecutter
Lecture: Adding the feature

Login or purchase this course to watch this video and the rest of the course contents.
0:01 Okay let's go back to the folder here
0:03 basically I want to open up this directory in the editor
0:05 so I click show in finder and it'll take me where the .gitignore was
0:08 which actually is right where I want to be, so I want to open this in PyCharm,
0:11 and on MacOS you can do that really nicely
0:14 by just dragging and dropping the root into PyCharm.
0:18 In Linux or in Windows you have to actually go file, open directory go find this thing.
0:23 So, you don't have to use PyCharm, I like it the best,
0:27 it's totally up to you on whether you want to do it or not.
0:30 PyCharm has built-in source integration, so let's say add root here
0:35 here you see all the things that we're going to work with
0:38 and this folder is actually where we're most interested
0:42 so let's let it do its little indexing, so we have autocomplete
0:44 and then we'll be ready to roll.
0:47 First thing I'd like to be able to run this inside PyCharm,
0:50 so there's a couple of options, let's go to this configuration,
0:53 say add a new Python run, and normally,
0:56 you would put the script here, you could even right click and say run it
0:59 but this is a package so that makes it kind of tricky
1:02 so we'll say script parameters, oops, not there, interpreter options -m
1:06 and then what are we going to do- we're going to say cookiecutter
1:09 and then who knows what we're going to give it here, right now I just run the help ok
1:13 So notice the right virtual environment was found because of the naming convention
1:19 PyCharm knows to load that one up,
1:21 also unnamed is probably not the best name
1:24 let's just call this cookiecutter, and we'll say single instance of that
1:28 okay, now if we hit run, we should see at the bottom error, no template
1:32 that's good that's actually okay right, that's what we wanted
1:36 we could pass in like -h for help or whatever
1:41 but you'll see like it's running down here now.
1:44 The other thing we can do if we want to fiddle with it
1:46 is we can run it in the terminal,
1:49 notice the terminal automatically activates the virtual environment
1:52 so we can just say cookiecutter -V to see which one
1:54 and it's the same one out of the same place
1:57 ok, so we are ready to run, this thing is set up locally
2:00 it's in our editor, let's go make a change.
2:02 Now, the part that we care about, the part I want to start exploring from
2:06 is from the CLI, so if you look at the CLI here, you can see it's using click
2:11 which is a thing to basically manage the command line interface for you
2:16 and down here, there's a bunch of stuff happening right,
2:19 is going to come down here and run of the cookiecutter for us.
2:23 And you can go see the various pieces that are being called,
2:27 and I would encourage you to sort of explore the flow from here on down
2:31 so you understand how all the pieces fit together,
2:34 there is some documentation and so on, but I've already done this,
2:37 I've already figured out where I want to go, so I'm going to go edit this location
2:41 okay, down here notice this is the stuff about config files
2:46 remember we're working on the YAML thing, that's the default config for the user;
2:51 here is where we're working, at the very root of everything,
2:57 whether we use a default config, a pass config, a user config,
3:00 we're going to be getting into this get_config() here, okay,
3:04 we actually will find that the error happens right here,
3:09 so let's go ahead and set-up our system,
3:13 so we can try that, let's see if we can make this thing fail basically,
3:16 so I want to say cookiecutter and I give it little output folder here,
3:20 cookiecutter cookiecutter-template -o ~/Desktop/test/ and let's just do something simple,
3:25 cookiecutter-template, alright, that runs, everything looks great.
3:33 Now, let's try that again, but first let's edit and make our YAML defaults broken.
3:40 It doesn't matter if this is our default file or some other one,
3:43 it's just by default this will be the one selected.
3:46 So I deleted that little bit there, let's try it again.
3:49 Let's see what mistake did we make- oh there is no pattern for github_username
3:55 what is going on, and if we see where that is, that's in config line 61,
4:00 which is right here, this is basically in this try accept block.
4:05 So what we need to do is add a little fix right here,
4:11 so let's do this, let's add a function, right up above here,
4:14 so we're going to call this function fix_missing_endline_in_yaml()
4:20 We're going to do that here, and what I actually want to do is
4:23 I want to sort of separate this out a bit here
4:25 so I want to say yaml_lines this is going to return actually a set of lines of text here
4:32 we want to pass this and instead of passing in here like so,
4:37 we want to create a yaml_text = "".join(yaml_lines)
4:44 put the lines back together, yaml text, okay.
4:47 So our goal now is to somehow get this value passed in here,
4:52 make some changes, get it back, so say yaml lines equals this
4:56 we'll say read lines which instead of returning the whole string,
4:59 the whole thing as a string, and we're going to actually return a bunch of lines
5:04 it's a little easier to work with it that way, so we'll come down here
5:07 and we'll say get all the lines from the original file
5:09 and then potentially modify them and then turn that back into a flat single string
5:14 which this was expecting, before.
5:17 Ok, so all we got to do is write this little function here
5:21 and what do we need to check for-
5:25 let's go ahead and pass in our yaml_lines, we'll return our yaml_lines,
5:29 ok so we're going to say if yaml lines we don't want to crash
5:32 if for some reason that's not there, and if the yaml_lines
5:37 the last entry is not equal to just a Newline, and it's Python 2 so Unicode,
5:44 if the last line in this file is not just a blank line,
5:48 all we have to do is say append a Newline, that's it,
5:54 this should actually fix our code, this should fix that annoying little bug in Cookiecutter
6:00 and it's six, eight lines of code, not too bad.
6:04 Let's try this now, let's just verify that we do have the missing piece here,
6:08 and let's try this again; ta-da, fixed.
6:11 How do I know it's fixed, what if I skip this little part right here
6:15 try it again, it crashes; put it back- fixed.
6:19 Okay, so I think this is a pretty cool little feature, this is not much work
6:24 PyCharm thinks this is misspelled, so I am going to say it's not,
6:28 so everything looks ok, the one thing that we should probably do is
6:31 let's go ahead and document this, add some document strings here and some there
6:35 so let's go ahead and add some docstrings here as well,
6:38 just so people come along know what this thing is about,
6:40 like why is this weird thing adding a Newline, maybe in some time
6:43 when poyo doesn't need it then we could take this away right.
6:47 Alright, so there is a little description I wrote beforehand
6:51 so it says if the YAML configuration file does not end with a single bank line
6:55 a cookiecutter exception invalid configuration
6:57 is thrown within an indecipherable error
7:00 I think we can all agree that's the current state,
7:02 this method fixes that by adding a trivial Newline if it is missing.
7:05 Save one more thing here, alright, it looks like it's still working, fabulous.
7:10 Okay, so let's go ahead and submit this back.
7:13 Now, probably it should be running the test here, right,
7:16 we should run all of our tests here,
7:19 so running our tests, with tox, give it a moment,
7:22 ok so it looks like all the tests ran fine, I don't have Python 3.3 or 3.4
7:27 but when we do the check in, the continuous integration and automated build system
7:33 has all of this stuff set-up, so you see like
7:36 flake 8, PyPy, Python 3.3 and 3.4 didn't quite work
7:39 but they'll work in the final version, as you'll see in a little bit,
7:43 but at least we saw it worked on Python 2.7 and Python 3.5
7:47 and that gives me a lot of confidence
7:49 that we didn't break anything during this process.
7:52 So, we just pip install tox, and then I just type tox and it runs all these tests, perfect.
7:59 So now we're ready, we've added our feature,
8:03 created our feature branch, added feature we've run the test
8:06 we're ready to check this in and create a pull request.