Displaying 1 to 16 from 16 results

module-best-practices - :books: some best practices for JS modules

  •    Javascript

This is a set of "best practices" I've found for writing new JavaScript modules. This guide deals specifically with front- and back-end Node/CommonJS modules hosted on npm, but the same concepts may apply elsewhere.A "module" is just a reusable chunk of code, abstracted into a more user-friendly API.

commitlint - 📓 Lint commit messages

  •    Javascript

commitlint is considered stable and is used in various projects as development tool.

go-critic - The most opinionated Go source code linter for code audit.

  •    Go

Go source code linter providing checks currently missing from other linters. Provide as many useful checks as possible; We're prototyping and experimenting here.

XS-Labs-Style-Guide - XS-Labs Coding Style Guide for C, C++, Objective-C and x86 Assembly


These are the coding conventions used for all recent XS-Labs projects. Feel free to comment, raise issues, fork and/or adapt this document. XS-Labs' coding conventions make a heavy use of whitespaces. It's not a common habit among coders, who usually prefers compact code.

gulp-esformatter - Beautify JavaScript code with esformatter

  •    Javascript

Issues with the output should be reported on the esformatter issue tracker.See the esformatter options.

conventions - documentation package for Go conventions

  •    Go

Learning the syntax and semantics of a language is only the first step for new developer. The second step is learning about the language ecosystem. Conventions is an example Go package that is loaded with documentation specifically targeting new developers that have done the Go Tour and have read the documentation on the "go" binary, but want to know more about writing packages and software.

Swift-Style-Guide - Swift language style guide & coding conventions followed by Xmartlabs.


Swift language style guide & coding conventions followed by xmartlabs.com team. Use descriptive names with camel case for classes, structs, enums, methods, properties, variables, constants, etc. Only Classes, Enums, Structs names should be capitalized. Don't care about name length.

go-namecheck - Source code analyzer that helps you to maintain variable/field naming conventions inside your project

  •    Go

Source code analyzer that helps you to maintain variable/field naming conventions inside your project. In big teams, same things end up being called differently eventually. Sometimes you bring inconsistencies on your own. Suppose it's considered idiomatic to call string parameter s if you can't figure a more descriptive name, but sometimes you see str names used by other programmers from your team. This is where go-namecheck can help.

conventions - GraphQL Conventions Library for .NET

  •    CSharp

GraphQL .NET has been around for a while. This library is a complementary layer on top that allows you to automatically wrap your .NET classes into GraphQL schema definitions using existing property getters and methods as field resolvers. More detailed examples can be found in the unit tests.

eslint-config - @anvilabs' ESLint configs

  •    Javascript

Anvilabs' ESLint configs, following our internal styleguide. See individual packages in packages.

tasty-commits - :lollipop: Simple commit message convention for easily digestible history streams


As a visual person, I find it difficult to read through large commit history logs in binary color schemes (i.e. black / white). In order to improve readability and understandability of my commit history I started prefixing my messages with emojis in a consistent manner.

PDF-Archiver - A tool for tagging files and archiving tasks.

  •    Swift

Archive all incoming documents digitally to access and search them in an easier way. Transfer the sorted documents to your smartphone or make a backup within seconds. This structure is independent from your OS and filesystem and makes it very easy to search files ...