Skip to content

Instantly share code, notes, and snippets.

View jlcarvalho's full-sized avatar

Jean Lucas de Carvalho jlcarvalho

View GitHub Profile
@jlcarvalho
jlcarvalho / combinations.js
Created November 29, 2017 17:32 — forked from axelpale/combinations.js
JavaScript functions to calculate combinations of elements in Array.
/**
* Copyright 2012 Akseli Palén.
* Created 2012-07-15.
* Licensed under the MIT license.
*
* <license>
* Permission is hereby granted, free of charge, to any person obtaining
* a copy of this software and associated documentation files
* (the "Software"), to deal in the Software without restriction,
* including without limitation the rights to use, copy, modify, merge,
class Questions extends React.Component {
render() {
return (
<div>
<h2>opaaaa</h2>
</div>
)
}
};

30 de outubro

PDF

  • Austar tamanhos de fonte para ficar parecido com o doc original
  • Ajustar espaçamentos
  • Adicionar @ecopowergoias no rodapé da última página
  • Quantidade de painéis está fixo na página 4
  • Testar nome de cliente muito grande no PDF

Outros

@jlcarvalho
jlcarvalho / conventional_commits.md
Last active August 31, 2022 02:49 — forked from ivanrosolen/conventional_commits.md
Guia para mensagens de commits

Guia para mensagens de commits

TLDR;

Nós utilizamos o Conventional Commits para padronizar as mensagens de commit, esse documento descreve o funcionamento desse padrão.

No entanto, para facilitar a nossa vida nós também usamos o Commitizen. Essa ferramenta nos ajuda a seguir a padronização através de uma CLI para realizar commits que pode ser acessado através do comando:

npm run commit
@jlcarvalho
jlcarvalho / part1.md
Created August 31, 2022 02:53 — forked from vlandham/part1.md
Feature Branches and Pull Requests : Walkthrough

Here's a little walkthrough of how Yannick and I are using feature branches and pull requests to develop new features and adding them to the project. Below are the steps I take when working on a new feature. Hopefully this, along with watching the process on Github, will serve as a starting point to having everyone use a similar workflow.

Questions, comments, and suggestions for improvements welcome!

Start with the latest on master

When starting a new feature, I make sure to start with the latest and greatest codebase:

git checkout master