 the time that I have issues. So when I type in a line of code and I forget to do something, he'll tell me also to do it. So I can see pretty quickly that I have issues on this line. So you're actually changing those to yourself? Right. So if you mouse over the dot, that's going to pull up a list of the errors. So on this line I have 21 errors. Holy cow. So you can go through and fix them. I don't have my spaces. I don't have that. This doesn't need to be on the same line. So it's all this little thing. It's kind of tedious. That's what the PHP sees. So hopefully you're not running this on a big old file. If that's the case, then you do want to use the purifier. As you're coding, the dot will pop up and you go, oh, this is the wrong one. In this case, it would be super tedious to go through and fix all these things one by one. You see, there's still an issue here. I don't know what to do. I don't see what the issue is on this one. That's beauty tools like this, right? My human eye, I'm not going to see all the little nifty things, but this is going to find it for me. It's so much easier to hear these fingers so that even though I've been perfect, the tools help to make the code better and more sustainable in the long run. So that is the demo. Oh, one more thing. So within your project, you have this XML file. It's called pgpcs.xml.disc. And what this does is this defines the standards of the rules that you want to use. So just because we have WPCS installed on our system, that doesn't mean we're necessarily using the rules. So this tells us if we scroll down, so config, minimum supported WPC version is 4.5, rule set is WordPress. So that's telling pgpcs, I want to use the WordPress rule set as an Azure step in this, right? And you can define all sorts of rules. So there's some co-negotiator rules that might confirm what we're doing. And for various reasons. And so you can actually turn off some of the standards, some of the specific rules. And that's what you, like some of these down here are. And I've got a comment about it because I didn't want to mess with those. But like, so you're, you want to prefix all the locals, for example. So any kind of local variable. You want to prefix that with the slug of your plugin or your theme so that it doesn't conflict with another plugin or another theme that might have the same thing. Things like that. So pgpcs, you can set those rules and set specific details of those rules as well. So that's what that problem is for. That's all I've got. So any questions, comments, criticism, compliments? And also, this is my Twitter. Do you want to ask questions on Twitter? Yes. I did a coding series, I'll do that. You can do that obviously. In terms of WordPress coding series, you want to do like a full echo of this. Because it's easier to read and see what's happening. So I know what that is. It's like what you just put, open a bracket, question mark, equals in the string and close it. That's just a real shorthand for, instead of doing PHP echo within the string, it's a shorthand. And I kind of like it better for some things, but it's, in terms of the standard, it's not what, it's not, it does not adhere to the WordPress coding standards. Especially from the custom fields. And so some add-ins have a grudge against the boss. So if I'm going to go to the site, they go into all these, you know, hack JavaScript codes in the custom fields. Well, you know, you've got to escape all that before it actually gets to the end user. I'm certain that it is, right. But I mean, again, I mean, ACF is, is, is. In general though, the rule is you should escape everything as late as possible, right. So as late as possible being, like, when you're echoing an echo, you have users, you need to escape it. It's, it, it, again, that's an annoying thing to have to escape. They should know on every little thing. But it's, it's, ultimately, it doesn't matter for you in practice to do that. I just can't, you can do it like this. You go, you do it like this. That's not as late as possible. Well, I think it's going to be in the echo. And again, it's kind of, because I agree with you, right. I would, I would rather feel that at least out of the way when people see it, but it's, it's, ultimately, it's better and more secure being a user. You know that doesn't make sense, like, when you're doing it. You have to think in terms of, like, down the road. If you're not the one, because you're, there's someone else who's had to go down the road. You want to make sure that everything's escape properly before it gets to the end user. Well, and just a point of clarification on that too. One thing, you know, if you're prescaping a variable and then it goes through any other functions, there's a possible, you know, injection at that point. And so that's why you want it as late as possible. Right. Especially so, like in WordPress, I mean, apply filters, right? I mean, if you apply, if any kind of filters would ever apply to anything, then you don't know what third-party filter changed that variable. Somewhere between advanced custom fields and when you get a hold of it, there's a filter happening that might be changing it within some kind of hacks in there. You know, the rest of it, right? Yes. You can do that. You do need to have, whenever you want, which standard you want to use. And so that's where, like, that's what the Sex About Law comes in. That's where, within your project, you're going to have something like this to tell PHPCS which standard you're using. Or within the command, if you run it on the command line, you use phpcs dash dash standard equals WordPress. And it'll, as long as the PCS is installed, it'll use WordPress standard when it's sniffing a code. But just in general, it's better to kind of encapsulate it within a project because you're sharing a project, you know, either with other developers within your team or it's like the source project you're sharing. So you want to, you want to have these things defined in any way in Composer and, like, produce something out. So to answer your question, yes, it's possible to do that. But I'm sure you do a lot of things like the PHP. So I found, so I've taken over a project. So you want to, but in general, I mean, like, it's just better to have the writing code the right way so that you don't have to, and also there to help you continue. There are ways that within this within, like, continuous integration tools like CircleCI, for example. Let me see if I have one. So this is a CircleCI configuration. You can get over it with install. Plans the dependencies there. It'll run your PHP CS for you. So we have a lot of projects where when we submit anything to GitHub, it's automatically going to run the CircleCI, or CircleCI's tools. And you can do any kind of learning. Yeah, so what, so it's pulling in, it's pulling in my project, and it's pulling in, like, it's a composer Json file. And so when you run the composer install, the composer got Json files, and it's telling you what dependencies that you need to be there. A lot of people might ask me, do I get the hallway, hallway checks, podcasts, and everybody else have that? It's really good, by the way. It's really nice people. And they found out I had a Json, so, like, we're talking about Json, most of the time, which is fun, right? And they're like, hey, what do you think about Json? What works as a worker? And I'm like, oh, Json's better. Yes. So personal views on ternary statements. I'm sorry, I said that again. Personal views on ternary statements. Uh, I mean, I like them. Now, say this standard, so everyone knows. It depends, right? I mean, like, it's a ternary statement. It's just basically a shorter, short form conditional. I like them, and they're actually not bad to use within ternary standards. As long as you don't overuse them, and as long as they're used in the right context. But, like, in general, like, just a full-on statement is way more readable than they want to be. Look at flags? Uh, no. So, that's your question. So, um, like, so we can put it like, the doc comment thing at the top. I mean, that should be at the top of every piece you value, right? And that should be on the description of what the file is. It should have a package. That's part of the RISO package being like the name of your theme that you're building. So, that's an established standard. And, um, another thing, and I don't know if this is a full-on word for a standard. It's just a VIP standard. But, like, if you're doing, like, a comment, like, a diss, what? So, if you're doing a comment like this already, like, you're doing a comment with this, um, you gotta put a period with the other. It's gonna be, like, a sentence. No. And that might just be anything. I'm just used to having to do it, so it's, which is in general, like, for my personal preference, comment the heck, because that's not gonna affect anything, right? So, put it, be as verbose. And, you know what I mean? Be very descriptive and comment everything, because you think about the next person. So, I think we're out of time, actually. So, I'm happy to hang out out here if you guys have more questions or talk about softball and doing one or whatever else. So, thank you so much for your time. Thank you.