Héctor Canto hectorcanto

I hereby claim:

To claim this, I am signing this object:

Overview

This is a list of shareable things under my GitHub account, being that gists or full repos

A list of software engineering vocabulary in English, Spanish, and Portuguese as I found them in my day to day

	def pytest_collection_modifyitems(items):
	"""
	Add marker to all tests in the conftest folder tree.

	You need to organize your tests in folders for it to work.

	Usage: `pytest -m $marker_expression`
	Example: `pytest -m unit1

	Reference: https://docs.pytest.org/en/stable/reference.html?highlight=collection_modi#pytest.hookspec.pytest_collection_modifyitems

	#!/usr/bin/env bash

	# SYNTAX branchtype/[subproject/]description_with_underscore-#CODE-123
	# Example feature/main_api/new_feature-#MAPI-123

	# Separators: slash (/) dash (-), don't use dashes as spaces, please

	# Why this syntax?
	# ticket at the end to keep autocomplete working in terminal
	# optional subproject for better CI pipeline decissions per subproject (multirepo, subapps, contexts ..)

	"""This is the docstring main line, I prefere them without a final dot

	Descritption goes after a brealine, first line should not be multiline but second can be.
	After it there can be many section like: Example, Usage, Returns, Attributes, Todo ... There
	might special notation for documentation tooling like Sphinx or Handsdown. In general avoid

	Avoid `Attributes` and `Returns` typing if specified in the hinting unless it is necessary for the tooling.

	This is based in: [Sphinx Napoleon](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html)