Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase.
[Brief description ]
- [more description]
- [more description]
- [more description]
This guide will provide a complete walkthrough for getting GitButler setup and functioning on a windows environment using Windows Subsystem for Linux (WSL).
Please note that GitButler on windows via wsl is not well tested and not officially supported, though one of the top priorities of the GitButler team is to get a working windows build out asap. For now, however this is the easiest solution I have developed.
{ | |
"editor.formatOnSave": true, | |
"python.linting.mypyEnabled": true, | |
"python.formatting.provider": "black", | |
"python.sortImports.args": [ | |
"--profile", | |
"black" | |
], | |
"[python]": { | |
"editor.codeActionsOnSave": { |
package com.alis.soft.socketIO.socketcontroller; | |
import com.alis.soft.socketIO.data.Message; | |
import com.corundumstudio.socketio.AckRequest; | |
import com.corundumstudio.socketio.SocketIOClient; | |
import com.corundumstudio.socketio.SocketIOServer; | |
import com.corundumstudio.socketio.listener.ConnectListener; | |
import com.corundumstudio.socketio.listener.DataListener; | |
import com.corundumstudio.socketio.listener.DisconnectListener; | |
import lombok.extern.log4j.Log4j2; |
package com.alis.soft.socketIO.config; | |
import javax.annotation.PreDestroy; | |
import io.netty.bootstrap.ServerBootstrap; | |
import io.netty.channel.ChannelInitializer; | |
import io.netty.channel.EventLoopGroup; | |
import io.netty.channel.nio.NioEventLoopGroup; | |
import io.netty.channel.socket.SocketChannel; | |
import io.netty.channel.socket.nio.NioServerSocketChannel; |
import asyncio | |
from pyppeteer import launch | |
from urllib.parse import urlparse | |
import http.client | |
import json | |
import logging | |
URL = 'https://example.metabase.com/dashboard/4' | |
USERNAME = 'username' | |
PASSWORD = 'password' |
# file: /laravel-project/.env.example | |
APP_NAME=Laravel | |
APP_ENV=local | |
APP_KEY= | |
APP_DEBUG=true | |
APP_URL=http://localhost | |
APP_SERVICE=laravel.test | |
APP_PORT=8000 |
######## | |
# app.py | |
######## | |
# Example of how I use it in my project. This file cannot be run as-is. | |
# The only difference with the example in the fastapi_singleton module docstring is | |
# the use of a subclassed FastAPI application to define type annotations | |
import fastapi | |
import fastapi_singleton |
To me, legacy code is simply code without tests. I’ve gotten some grief for this definition. What do tests have to do with whether code is bad? To me, the answer is straightforward, and it is a point that I elaborate throughout the book: Code without tests is bad code. It doesn’t matter how well written it is; it doesn’t matter how pretty or object-oriented or well-encapsulated it is. With tests, we can change the behavior of our code quickly and verifiably. Without them, we really don’t know if our code is getting better or worse.
Four Reasons to Change Software: For simplicity’s sake, let’s look at four primary reasons to change software.
""" | |
A simple proxy server, based on original by gear11: | |
https://gist.github.com/gear11/8006132 | |
Modified from original to support both GET and POST, status code passthrough, header and form data passthrough. | |
Usage: http://hostname:port/p/(URL to be proxied, minus protocol) | |
For example: http://localhost:5000/p/www.google.com | |
""" | |
import re |