| // Chi-like syntactic sugar layer on top of stdlib http.ServeMux. | |
| package main | |
| import ( | |
| "net/http" | |
| "slices" | |
| ) | |
| type ( | |
| middleware func(http.Handler) http.Handler |
| /* Using a JavaScript proxy for a super low code REST client */ | |
| // via https://dev.to/dipsaus9/javascript-lets-create-aproxy-19hg | |
| // also see https://towardsdatascience.com/why-to-use-javascript-proxy-5cdc69d943e3 | |
| // also see https://github.com/fastify/manifetch | |
| // also see https://github.com/flash-oss/allserver | |
| // and https://gist.github.com/v1vendi/75d5e5dad7a2d1ef3fcb48234e4528cb | |
| const createApi = (url) => { | |
| return new Proxy({}, { | |
| get(target, key) { |
Rust error handling is nice but obligatory. Which makes it sometimes plenty of code.
Functions return values of type Result that is "enumeration". In Rust enumeration means complex value that has alternatives and that alternative is shown with a tag.
Result is defined as Ok or Err. The definition is generic, and both alternatives have
| const templatized = (template, vars = {}) => { | |
| const handler = new Function('vars', [ | |
| 'const tagged = ( ' + Object.keys(vars).join(', ') + ' ) =>', | |
| '`' + template + '`', | |
| 'return tagged(...Object.values(vars))' | |
| ].join('\n')) | |
| return handler(vars) | |
| } |
| [ | |
| { | |
| "name":"Anti-mage", | |
| "Health":[ | |
| "500", | |
| "1000", | |
| "2000" | |
| ], | |
| "Mana":[ | |
| "100", |
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
| /** | |
| * Hypertext Transfer Protocol (HTTP) response status codes. | |
| * | |
| * @see {@link https://en.wikipedia.org/wiki/List_of_HTTP_status_codes} | |
| */ | |
| export enum HttpStatusCode { | |
| /** | |
| * The server has received the request headers and the client should proceed to send the request body | |
| * (in the case of a request for which a body needs to be sent; for example, a POST request). |
This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.
| ### Setup Import File and Permission Set | |
| # Step 1. Export the RecordTypes | |
| -> sfdx force:data:tree:export -q "SELECT ID, Name, DeveloperName, SobjectType FROM RecordType" -o data | |
| Wrote 1 records to data/RecordType.json | |
| # Here is what the export might look like | |
| -> more data/RecordType.json | |
| { |