DEV Community: Milo

Cloning, how does it work?

Milo — Thu, 21 Oct 2021 21:23:01 +0000

Hey!
Recently, I have been faced with an error. I have a DasHap of a &str and a bool, and I have 2 functions, each in a loop, each in their own thread. I need to share this dashmap between both threads, so I wrapped it in Arc. I get a borrowing error, of course, and was suggested to clone outside of the thread because the closure is async move. But, then, if I update the not-cloned value, that won't reflect on the cloned-value, and to update the cloned-value, I have to reference it where the not-cloned value changes, which is in a thread, that would cause borrowing errors.
To sum up, having a value being cloned outside of a loop, requiring the original value to be updated, subsequently also requires the cloned-value to be update, but can't be done as if I update the cloned-value in thread 1, I can't use it in thread 2 because of borrowing errors.

Any help appreciated!

Imagine Git hooks in Rust..

Milo — Sat, 28 Aug 2021 13:20:28 +0000

I'm going to say it.... Git hooks are bad.

Well, not bad, just annoying, and way too much setup. You have to write a bash script, etc, and things like husky simplify it.. but not enough.

I wrote something a few months ago called Glitter, with its sole purpose being a commit message templating system. It works fantastic, but recently I had someone create an issue: https://github.com/Milo123459/glitter/issues/33

They basically asked for Git Hooks in Glitter. I'd already implemented a task system (so you could do something like glitter fmt or glitter cc fmt) just by using a simple bit of config, but I thought that just like the user suggested, automatically running them before git add . in the push command.

Some benefits:

Git Hooks can be quite slow
Git Hooks can sometimes not pick up paths of packages installed with npm
Simple config, and can be setup in less than 30 seconds

So lets look at something to format our Rust code before we push.

{
  ...
    "custom_tasks": [
        {
            "name": "fmt",
            "execute": [
                "cargo fmt"
            ]
        },
        {
            "name": "lint",
            "execute": [
                "cargo clippy --all-features --all-targets"
            ]
        }
    ],
    "hooks": [
        "fmt",
        "lint"
    ]
}

... is other config. Check out this post if you want to know how to initially set it up.

Right, it's quite a lot to take in, lets break it down.

custom_tasks are tasks that we can run, or, alternatively, can be used as hooks. From this example, I can do glitter fmt (or glitter cc fmt) and it'll run cargo fmt. If I ran glitter lint (or glitter cc lint) it'll run cargo clippy --all-features --all-targets, and so on.

We can then reference these tasks in the hooks field. This field takes in the name of your tasks and will just run the commands specified in the execute field.

Problems I faced

Things like yarn (or any NPM package installed with npm globally) wouldn't be picked up in the path. I was able to fix this rather simply by using the crate which which allows me to get a path to an executable (or a shell script) to run to run the cli. This can also sometimes be a bit faster than just running the name of the command (ie, it'll be faster if I provide a path to yarn, and don't run yarn itself)

Additional info

Hooks will exit and cancel the command if the command fails or it's exit code is not 0. It's very simple.

If you feel this is cool, please leave a star on the repo.

Feature requests can be put in issues on the repo if possible. If you have any questions, you can make a discussion or ask in the comments.

Thanks!

Introducing coco

Milo — Thu, 29 Jul 2021 02:49:19 +0000

Hey,

Recently I have been running a lot of curl scripts, and they get annoying to google, copy and paste into the terminal. I built coco to fix that.

Coco provides a simple CLI to add scripts with full argument support, so you can make curl requests faster.

Lets say I want to get someones GitHub contributions:

coco add contributions "https://github-contributions-api.deno.dev/+1.term"```



Now, I can type `coco contributions GITHUB_USERNAME` and that'd template out to `https://github-contributions-api.deno.dev/GITHUB_USERNAME.term`

It's simple but does the trick. I plan to add more features that get suggested.

If you want to star the repo, here is the link. https://git.io/coco

Thanks, and, hope coco helps you out somehow.

Svelte & vscode & typescript odd error

Milo — Tue, 18 May 2021 12:33:25 +0000

hey, im using svelte for a project and vscode extension, and im using typescript, i have it structered like so: src/webviews/
tsconfig.json
components/Sidebar.svelte
pages/Sidebar.ts
this is the error
not sure how to fix it?
anyone know?

code: https://github.com/Milo123459/salt/tree/master/vscode-salt

Please, anything will help! I'm so confused.

Salt - 🚀 Task managment++

Milo — Sun, 16 May 2021 17:44:24 +0000

For so long, I've been using github issues to keep track of things I need to do. It gets annoying, relying on a server to respond, and waiting a while. Say less my friends, I have a solution!

salt - A better way to keep track of tasks. No server, everything is local and can be organized very easily. No more "oh hey that's where it was", more "oh god I have to write code!"

Jokes aside, salt is an attempt to redefine task management. With a VSCode extension in development, for the ultime experience, and tasks synced with other platforms (wip) you can basically throw away anything else.

Concepts

Nodes (not nodejs 🚀)
Tasks
Task status

Node

A node is the parent of some tasks, think of it like a tree, where the tree is the node, and the apples are the tasks, all under one big node.

Tasks

Something you have to do...

Task status

Either checked, or not checked, this allows you to keep track of tasks you have to do!

Why

Why not? A task management system for the CLI is the one thing I've needed for so long, and I spoke to a few friends and they loved the concept and using it as well.

How

Rust. The CLI is pure Rust.

Install

# macos
brew tap eternalmoon1234/brew
brew install salt
# windows
scoop bucket add sushi https://github.com/kidonng/sushi
scoop install sushi/salt
# other
curl -fsSL https://raw.githubusercontent.com/Milo123459/salt/master/install.sh | bash

Thanks for reading! Suggestions can go in the comments 😉

Introducing: Glitter!

Milo — Wed, 24 Feb 2021 17:33:25 +0000

Hey folks! I've been hard at work programming my first commercial package.

This package is called glitter. A hyper-fast way of executing git commands.

Currently, glitter is available on Scoop. Install it with scoop install glitter, or, clone the repo and run cargo install --path . to install it.

So what is glitter?

Glitter is the git-companion you've longed for. Fast, efficient, written in Rust and super friendly errors. What more could you need in a friend? 😃

But.. how do I use it?

The config lives in a file called a .glitterrc (this is customisable!) and is a simple JSON structure. See all available keys here.

If you have a question, please don't hesitate to make a discussion on the repo

Let me know of some feedback in the comments, hope you have a great day!