Viktor Klymentiev

In JS, how to remove all cookies and disable them?

2022-10-24T15:59:51.820Z

For situations, like, for example, a user withdraws their consent to use cookies, you can delete all existing cookies:

function deleteCookies() {
    var theCookies = document.cookie.split(';');
    for (var i = 0 ; i < theCookies.length; i++) {
        document.cookie = theCookies[i].split('=')[0] + '=; path=/; expires=Thu, 01 Jan 1970 00:00:01 GMT;';
    }
}

And then disable them by overriding a getter and setter:

if(!document.__defineGetter__) {
Object.defineProperty(document, 'cookie', {
    get: function(){return ''},
    set: function(){return true},
});
} else {
    document.__defineGetter__("cookie", function() { return '';} );
    document.__defineSetter__("cookie", function() {} );
}

In console, how to stop or remove all Docker containers?

2022-01-22T11:08:39.368Z

One-liner to stop or remove all of Docker containers:

docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)

#docker

#howto

In Git, how to squash commits?

2021-12-20T10:07:31.296Z

First, let's find out how many commits need to be squashed into one. This command will show you what commits you have added compared to the master branch:

git cherry -v master

And this one will show you how much of them:

git cherry -v master | wc -l

For example,

> $ git cherry -v master
+ edb880bb972736eebdc86c55a158e659c787b769 check url
+ 16817774ffc4ece00d9a7c75cf26f9a93cd90eda improved readability
+ 8db9d67018394a5a1e1215943ddfe002a25ccc08 tests

> $ git cherry -v master | wc -l
       3

Great! I have 3 commits ahead master. Now I want to rewrite history since HEAD~3, i.e. from what was 3 commits ago. To do this, I do:

git rebase -i HEAD~3

The -i flag means interactively. I have a file like this:

hint: Waiting for your editor to close the file... 
pick edb880bb check url
pick 16817774 improved readability
pick 8db9d670 tests

# Rebase 10def359..8db9d670 onto 10def359 (3 commands)
#
# Commands:
# p, pick <commit> = use commit
# r, reword <commit> = use commit, but edit the commit message
# e, edit <commit> = use commit, but stop for amending
# s, squash <commit> = use commit, but meld into previous commit
# f, fixup [-C | -c] <commit> = like "squash" but keep only the previous
#                    commit's log message, unless -C is used, in which case
#                    keep only this commit's message; -c is same as -C but
#                    opens the editor
# x, exec <command> = run command (the rest of the line) using shell
# b, break = stop here (continue rebase later with 'git rebase --continue')
# d, drop <commit> = remove commit
# l, label <label> = label current HEAD with a name
# t, reset <label> = reset HEAD to a label
# m, merge [-C <commit> | -c <commit>] <label> [# <oneline>]
# .       create a merge commit using the original merge commit's
# .       message (or the oneline, if no original merge commit was
# .       specified); use -c <commit> to reword the commit message
#
# These lines can be re-ordered; they are executed from top to bottom.
#
# If you remove a line here THAT COMMIT WILL BE LOST.
#
# However, if you remove everything, the rebase will be aborted.
#

Here's a list of my commits and a big comment on what I can do. From the list of commands, you can see that we can use squash or fixup in order to squash commits. The first is useful when you want to change the commit message, and the second when you want to use the commit message of the first. So, to squash all the commits, I do like this:

hint: Waiting for your editor to close the file... 
pick edb880bb check url
squash 16817774 improved readability
squash 8db9d670 tests

# Rebase 10def359..8db9d670 onto 10def359 (3 commands)
#
# Commands:
# p, pick <commit> = use commit
# r, reword <commit> = use commit, but edit the commit message
# e, edit <commit> = use commit, but stop for amending
# s, squash <commit> = use commit, but meld into previous commit
# f, fixup [-C | -c] <commit> = like "squash" but keep only the previous
#                    commit's log message, unless -C is used, in which case
#                    keep only this commit's message; -c is same as -C but
#                    opens the editor
# x, exec <command> = run command (the rest of the line) using shell
# b, break = stop here (continue rebase later with 'git rebase --continue')
# d, drop <commit> = remove commit
# l, label <label> = label current HEAD with a name
# t, reset <label> = reset HEAD to a label
# m, merge [-C <commit> | -c <commit>] <label> [# <oneline>]
# .       create a merge commit using the original merge commit's
# .       message (or the oneline, if no original merge commit was
# .       specified); use -c <commit> to reword the commit message
#
# These lines can be re-ordered; they are executed from top to bottom.
#
# If you remove a line here THAT COMMIT WILL BE LOST.
#
# However, if you remove everything, the rebase will be aborted.
#

Then git glues the commits and prompts me to enter the commit message (shows the commit messages of all the merged commits). You can leave it as is or change to whatever you want.

Finally, save the file and quit the editor. You can now type git log and see your single commit that contains 3 commits we were squashing.

Don't forget to force-push like you do after any rebase:

git push -f

That's it. Enjoy!

#git

#howto

In Git, how to change the default editor?

2021-12-19T15:56:17.833Z

As you know, for many specific operations git opens a text editor. On macOS and Linux, this is Vim by default. Not the most beginner-friendly editor I'd say. To make you comfortable, set your favorite editor as the git editor with just one command:

git config --global core.editor "path to your editor with params"

Then check it by making a commit:

git commit --allow-empty

Your favorite editor should open. Write a commit message, save and close the file. See git log to look for a commit. Is it there? If yes, you’re awesome.

Here are the commands for the popular editors:

VS Code

In VS Code press ⌘⇧P and select Shell Command: Install 'code' command in PATH from the list. Then run:

git config --global core.editor "code --wait"

TextEdit

git config --global core.editor "open -W -n"

Atom

git config --global core.editor "atom --wait"

Sublime Text 3

git config --global core.editor '"/Applications/Sublime Text.app/Contents/SharedSupport/bin/subl" -n -w'

#git

#howto

In Elixir, is there a way to determine if a module exists?

2021-12-18T16:43:03.967Z

You can use Code.ensure_compiled?/1, but there is a side effect: it will also attempt to load the module if it is not already, which may not be desired (depending on the use-case).

Here is an approach that should work without any side effects:

iex> function_exported?(String, :__info__, 1)
true

iex> function_exported?(NoModule, :__info__, 1)
false

Elixir modules export :__info__/1 so testing for it provides a generic solution.

#elixir

#programming

#howto

Okay, Houston, we've had a problem here

2021-12-13T15:47:06.039Z

Today I decided to create my own blog to share with you folks some expert advices, tips and tricks I face at my work projects. It wasn't easy. Actually, this is the third attempt to create a blog today. 🤦‍♂️ Something went wrong during previous two tries – my newly created blog has disappeared. Like I never created it before. Hope it doesn't happen again. :)

As you already know, not every problem can be easily solved by googling, so I hope this blog will be helpful in that direction. It also should be useful for me, because over time I forget many things that are difficult to recover.

Well, yay! 🙌 Have a nice day and see you in the next post!