Граф коммитов

4 Коммитов

Автор SHA1 Сообщение Дата
AsafMah d24ea97a48
Formatting throws like jetbrains (#259)
* format

* merge

* merge

* More files
2022-07-11 15:33:44 +03:00
Yihezkel Schoenbrun e03932ceb7
Black: Roll back requiring there be no newline after a field's annotation (#256)
* Black: Propose rolling back requiring there be no newline after a field's annotation. Alternatively, I propose requiring that there *be* a newline after a field's annotation.

As discussed previously, my perspective is that if one code style isn't clearly better than alternatives, the best approach is to let the devs decide. We don't need all aspects of code style to be 100% conforming in all ways, and taking away freedom unnecessarily from devs makes devs sad.

* Fix black

* Fix black

Co-authored-by: AsafMah <asafmahlev@microsoft.com>
2022-07-03 15:42:13 +03:00
AsafMah ca04a5881a
Formatting - compact (#236)
* Revert "Add formatter plugin (#231)"

This reverts commit f23b0780ca.

* Formatting - compact
2022-03-31 09:58:33 +03:00
AsafMah f23b0780ca
Add formatter plugin (#231)
* Added formatter plugin, right now only starting

* Put config on main file

* Updated style to match ours better.

* Added declaration.

* edit build.yml

* Update style and apply formatting

* Update style and apply formatting

* Tweaked settings again

* Replace with session because that might be the correct path.

* Try formatting

* line endings

* renormalize new lines

* csluuid

* new lines

* new lines

* Run again with clean

* fixed build.yml

* Changed style to be better

* Added some docs
2022-03-29 15:40:49 +03:00