pollutri
/
res_levis_backend
1
0
Derivar 0
Código Questões 1 Pedidos de integração 0 Lançamentos 0 Wiki Trabalho
Não pode escolher mais do que 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
369 Cometimentos
3 Ramos
9.3 MiB
 
 
 
 
Árvore: d2300aa400
Ramos Etiquetas
${ item.name }
Criar ramo ${ searchTerm }
de 'd2300aa400'
${ noResults }
res_levis_backend/cmd
Blaz Smehov d2300aa400 feat: implement basic API, reimplement Redis and some methods for quick insert (persistence in case of crash) using hash maps há 1 semana
..
bridge feat: boilerplate for settings handler, chore: refactor kafka client package name há 4 semanas
decoder chore: refactor and move code for beacon logic há 1 semana
location chore: add additional logs há 1 semana
server feat: implement basic API, reimplement Redis and some methods for quick insert (persistence in case of crash) using hash maps há 1 semana
testbench feat: basis for decoding different beacon types há 2 semanas
valkey-testbench feat: implement basic API, reimplement Redis and some methods for quick insert (persistence in case of crash) using hash maps há 1 semana
README.md Update cmd/README w/updated example URLs há 3 anos

README.md

/cmd

Main applications for this project.

The directory name for each application should match the name of the executable you want to have (e.g., /cmd/myapp).

Don’t put a lot of code in the application directory. If you think the code can be imported and used in other projects, then it should live in the /pkg directory. If the code is not reusable or if you don’t want others to reuse it, put that code in the /internal directory. You’ll be surprised what others will do, so be explicit about your intentions!

It’s common to have a small main function that imports and invokes the code from the /internal and /pkg directories and nothing else.

Examples: