<FromGitter>
<eliasjpr> @Brodan you can modify that behavior just edit the .amber.yml file to not run test of file changes
<FromGitter>
<Brodan> ah true good call!
<FromGitter>
<Brodan> @drujensen can you explain what the `password=` granite function in the auth module is doing? is the trailing equals sign a crystal convention of some kind? it doesnt look like that function gets called anywhere either
<FromGitter>
<damianham> @brodan that is a Crystal and Ruby convention to specify a setter method so that when your code does ```password = 'mysecret'``` it does something like 'method.send('password=', 'mysecret') which calls the 'password=' method with the arg. If you wanted to you could add a command to create and migrate the db before running the tests ⏎ ⏎ ```code paste, see link``` ⏎ ⏎ Welcome aboard!
<FromGitter>
<andrewc910> @Brodan Side note: when you do MyClass.new(name: "Andrew"), typically the "name=" will be invoked. This is how plain crystal and ruby work.
<FromGitter>
<andrewc910> With granite, you currently have to invoke setters yourself.
<FromGitter>
<Brodan> thank you @damianham and @andrewc910 ! This community has already been so welcoming and helpful. I'm so excited to start giving back to it soon!
<FromGitter>
<adacosta> sorry for the newb question ... working on the Amber framework code, what's the most simple way to recompile and run a core test?
<FromGitter>
<adacosta> if I make a single line change to an Amber framework test and run it with ⏎ eg. ```bin/amber_spec spec/amber/websockets/client_sockets_spec.cr:29```, it installs all of the dependencies again. Is there a more efficient way to do this so my test can be quickly invoked?