Had a not so obvious issue pop up recently in a Vue.JS app I’ve been working on for a while now. I have a table of members and if you click the member name, you get redirected to their profile page. There is a click event on the name link so it will store the profile id then use the router to push the new route. The issue is that when you click the link, you get the following error:
BUT if you click the link a second time you get redirected to the profile page as expected. This error is basically saying you can’t navigate to the same page you are on. Which is not what I was trying to do. So I was confused.
Turns out everything was working properly in my code I just didn’t account for it all. Here is my original link:
The trouble is the href=”#” is firing before my @click event fires. So, Vue’s router thinks I’m trying to go to the same page. To make the behavior what I wanted, I had to prevent that from firing and just fire my @click event.
Thankfully, Vue makes it pretty easy. Just add .prevent to your @click event. My new link looks like this:
The MacOS treats files which start with a period (.) as a hidden file. Say, something like .gitignore. And there are times where you want to actually see these hidden files. To do so, you can run some Terminal commands that affect the system. OR you can do a simple key command. Like so:
⌘⇧. will toggle the AppleShowAllFiles setting
This way you can turn them on/off quickly and easily without mucking in the Terminal.
Windows 10 has a built in Clipboard Manager which will let you copy multiple items — text or images — to your clipboard. Then later you can select from the list of items copied and paste them back in the order you choose.
You can turn it on (it’s off by default) by going to :
Start > Settings > System > Clipboard
Here you can also sign in so you can sync your clipboard across devices.
To use the Clipboard Manager, instead of Ctrl+V to paste you use:
Windows logo key + V
This shows a list of things copied and you select which one you want.
You can also select the triple dots menu on an item for additional options.
Sometimes, when you have a long file, it’s convenient to fold/collapse all the code regions so you can get a big picture of your file. In Visual Studio (the full blown IDE from Microsoft), it’s a simple keyboard shortcut combination
Thankfully, Visual Studio Code has something similar. To fold ALL regions use
Then just use the following to unfold the code file
The nice thing about this is that all the sub regions are folded as well. So you can simply open one region and all the items inside are still folded.
If you are intrigued by the idea of switching from the resource hog that is Google Chrome to the new kid on the block, Microsoft Edge BUT you have some killer Chrome extensions you just can’t live without…Then fear not! You can configure Edge to use a Chrome plug-in.
Ok, now that Edge is installed you can add your extensions. First, click the triple dots in the upper right-hand corner. Then select Extensions from the menu.
Before you go to the effort of getting a Chrome extension, first check for the extension in the Microsoft Store (link in the settings). What you want may already be there.
If you don’t find what you’re looking for then toggle the Allow extensions from other stores setting in the bottom left-hand corner.
Then navigate to the Chrome Web Store and search for your desired extension. Click the Add to Chrome button.
Edge will give you a pop-up asking if you want to add the extension, click the Add Extension button.
This will add the extension and you should get a notification that the extension was added to Edge.
Badda-bing, badda-boom! Your Chrome extension should now be installed in Edge and running just like the ones from the Microsoft Store. With full rights and privileges. You can disable or delete them just the same.
One last nice thing Microsoft has done is to segregate the other sourced extensions from those from their own store. That way you can easily find them.
As a developer, I have to copy and paste. A lot! Sometimes I need to copy several items from different locations and then paste them into the same file. This can be very tedious with the traditional Ctrl+C then Ctrl+V process. To help remedy this, I use Comfort Clipboard Pro, a very powerful clipboard manager. I realize for some this may be a bit of overkill or they don’t wish to spend the money on a solution.
Thankfully, Visual Studio 2019 has a feature which can help. Simply copy several items in a row using your preferred method — from the file menu or with a key command. Then place your cursor where you wish for the copied items to be pasted. Next, go to Edit in the file menu and select the Show Clipboard History option (alternately you can press Ctrl+Shift+Insert).
This will display a popup list of the things you’ve just copied. Click one of the items in the list.
The item you selected will be pasted into your file where your cursor currently sits.
That’s it! Quick. Simple. It didn’t require any additional software. And it didn’t cost you anything. Hope that helps!
Visual Studio 2019 shipped on April 1st. And one of the nice things about it is you can have it installed side-by-side with other version — like Visual Studio 2017. Most developers have spent some time selecting which features of Visual Studio they need installed. A nice addition to the new Visual Studio Installer is you can export your configurations from one version and import into another. So, if you’ve just installed 2019 and wish for it to be configured like your 2017 version, now you can! And it’s pretty straight forward.
Launch the Visual Studio Installer.
And that’s it! The installer will download and install any needed components based on your older configuration file.
To be helpful, browsers will cache information you enter in a form field. Then when you comeback and start typing, the same information will pop up near the field so you can click it to have it auto-entered for you. While this is useful, there are times you don’t want this behavior — like a one-time PIN number or CVC code for credit card payment.
Thankfully, there is an easy fix. On either the form itself or the specific fields you wish to stop this behavior, you can add the autocomplete property and set the value to “off“.
This accomplishes 2 things. It tells the browser not to save the data for use later. And it stops the browser from caching the data in session history.
This will work with most modern browsers….with one exception. Most modern browsers will not comply with the autocomplete=”off” for login fields; whether on the form or a field itself. It has to do with the way browsers handle password saving/creating internally. So just keep that in mind.