-
cp.nvim
Discontinued Competitive programming neovim plugin [Moved to: https://github.com/nullchilly/cpeditor.nvim]
-
cpeditor
The IDE for competitive programming :tada: | Fetch, Code, Compile, Run, Check, Submit :rocket:
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Here is the repo: https://github.com/nullchilly/cp.nvim
It aims to be a 1 to 1 clone of https://github.com/cpeditor/cpeditor/ thanks to u/ouuan
Check out luacheck. It can help spot typos or mistakes you've made and warn against anti-patterns. I'd honestly only look into setting it up locally because there's no benefit to putting it in a CI pipeline unless you have one for another reason IMO. This should be all the config you need:
Check out StyLua if you want a code formatter.
Check out plenary.nvim's test harness for unit tests and integration tests. The docs for setting it up are pretty good, but if you want a real-world example you can look at how I have tests set up in my plugin. It has unit tests (tests/$MODULE_spec.lua) and integration tests (tests/full_spec.lua).
This scenerio is what I was talking about, there is a local problem = problems.current_problem on every single line. Can I do something about it or it is what it is?