Let’s try to delete a user: > stroy(1)ĪctiveRecord::RecordNotFound: Could not find User with id=1 Loading development environment in sandboxĪny modifications you make will be rolled back on exitĪs indicated, any database changes you make will be rolled back when you exit the session. That’s when you’re glad you know about the -sandbox option: $ rails console -sandbox Sometimes you’d like to experiment with data in the console without the fear of permanently changing data. The console is generally a fun environment to play around in, but it can feel a bit too “live” if you have to worry about goofing up the database. > irb app > get "/movies" => 200 > get "/users/1" => 302 Playing in the Sandbox
#Iterm2 clear line movie
Suppose you have a Movie model that you previously used in the console and now you want to use it to run a query. Yup, the console has autocompletion support, too. So once you get comfortable with this shortcut, you save time in both environments. Searching with Ctrl + R also works on the standard command line. Or continue to press Ctrl + R to successively walk back through matching commands. Or press any arrow key to start editing the command. Once you’ve found the command you’re looking for, press Enter to run it. The more you type, the more it narrows down the search. It will search backwards in the history and autocomplete the first command that matches what you typed. There’s gotta be a better way, and indeed there is! If you’re on a Unix machine and using the default bash shell, then you can search for a prior command by pressing Ctrl + R and then typing any part of that command. Once you’ve gone back, you can go forward using the down arrow key.Īs your session history builds up, finding what you’re looking for using the arrow keys can be more work than just re-typing the code. Keep hitting it to scroll further back in time. To recall the previous line you entered, hit the up arrow key. The console maintains a history of commands which you can navigate using the up and down arrow keys. You’ve got a couple options for recalling commands.
#Iterm2 clear line code
Once you’ve run a line of code in a console session, you often want to re-run the same code later or edit it to do something slightly different. After calling reload! you’ll need to reinstantiate objects that have changed.
For example, if you have a movie object initialized in the console and then in your editor you define a new method in the Movie class, the movie object won’t have that new method even when you call reload!. Instead, use the reload! command to pick up the latest version of your code: > reload!Īny objects that existed prior to the call to reload! still reflect their previous version. You can refresh the code by exiting the console and starting a new session, but that’s tedious to do every time you change code. Once a file has been loaded, it’s cached for the duration of the console session. The console also runs in the development environment by default, but it does not automatically reload code. This works because your application code is automatically reloaded on every request when you’re running in the development environment. You can make code changes in your favorite code editor, then hit Reload in your browser to quickly see the effect of those changes. The Rails development environment is streamlined for rapid feedback.
#Iterm2 clear line windows
The Windows cls command clears the screen, and the Ruby system method runs that command in a subshell. If you’re on Windows, the only way we’re aware of to clear the console is by typing system('cls').
#Iterm2 clear line mac
You can also use Ctrl + L to clear the screen, which works on both Mac and Linux. To get a clean slate in your console, use Command + K on the Mac. To help you get the most out of your time in the console, here’s a collection of shortcuts, tips, and tricks. And once you’re comfortable using the console during development, it feels quite pedestrian to have to go through the front-door browser. Using the console lets you interact with parts of your app directly from a command-line interface without going through a browser. It’s like a back door to your application. As a Rails developer, you’ll end up spending a lot of time in the Rails console.
0 kommentar(er)
