Borrar branch: "master" y un poco de docs

[JohnGolgota]

eso... borrar la branch que no tiene uso.

• [x] Borrar la branch: "master"

• [x] #9

  Sugerencia primaria Vitest, secundaria Cypress, y no conozco más, tampoco conozco para el testing del back

• [x] #8

@Kolozuz @DuvanArwenLazar

About documentation

• Buscamos tener un registro muy completo del desarrollo de la aplicación por lo que entre mis recomendaciones personales esta: responder con sus opiniones, objeciones. sugerencias y esa monda. para tener el registro,

• Generar issues respectivas a cada punto del desarrollo y cosas así, ya lo discutiremos.

[Kolozuz]

No se le ofrece un cafecito también?

El mar, 25 de abr. de 2023 10:17 p. m., JohnGolgota < @.***> escribió:

Assigned #2 https://github.com/Lana-Software/Lana-App/issues/2 to @Kolozuz https://github.com/Kolozuz.

— Reply to this email directly, view it on GitHub https://github.com/Lana-Software/Lana-App/issues/2#event-9098542543, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2LSXYIXVOCEBSOJK6YYXPLXDCHUVANCNFSM6AAAAAAXL2L4R4 . You are receiving this because you were assigned.Message ID: @.***>

[JohnGolgota]

prefiero un capuchino gracias

Falta Supabase, Firebase o algo de eso

[JohnGolgota]

No se le ofrece un cafecito también? El mar, 25 de abr. de 2023 10:17 p. m., JohnGolgota < @.> escribió: … Assigned #2 <#2> to @Kolozuz https://github.com/Kolozuz. — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2LSXYIXVOCEBSOJK6YYXPLXDCHUVANCNFSM6AAAAAAXL2L4R4 . You are receiving this because you were assigned.Message ID: @.>

Si y se me olvido una tarea:

• [x] Borrar la branch: "master"

[Kolozuz]

question:

should we put de documentation here in the repository? in a docs folder? or where should we store that shi*, doing it here would be cool since we can use markdown, but maybe using Notion pages is a better idea(?), just tell me and I'll create them and share it here

[Kolozuz]

Doing some research regarding backend testing, for projects like ours Jest seems to be the what we're looking for, I'll dive into the docs but at first glance it seems pretty straight forward with almost no configuration needed.

[JohnGolgota]

I think the documentation can be use both notion to order the docs and issues to generete. Add README.md to proyect folders for quick docs and instructions for used

question:

should we put de documentation here in the repository? in a docs folder? or where should we store that shi*, doing it here would be cool since we can use markdown, but maybe using Notion pages is a better idea(?), just tell me and I'll create them and share it here

Jest i seen it(?) and hate, that it's the most popular in php backend projects

Doing some research regarding backend testing, for projects like ours Jest seems to be the what we're looking for, I'll dive into the docs but at first glance it seems pretty straight forward with almost no configuration needed.

[Kolozuz]

I think the documentation can be use both notion to order the docs and issues to generete. Add README.md to proyect folders for quick docs and instructions for used

Great, we'll do both then!

Jest i seen it(?) and hate, that it's the most popular in php backend projects

Alright, so perhaps we should take a not so popular approach? maybe something like Mocha, seems pretty easy to use as well, which i think is what should be taken into consideration, rather than if it's popular o not 😕

[Kolozuz]

Issue gets closed as last two tasks get moved to individual issues (including their info)