Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pgilad
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
1.
▲
Getting Real with LLMs
(giladpeleg.com)
2 points
by
pgilad
10mo ago
|
1 comments
2.
▲
by
pgilad
10mo ago
What real-world problems can be solved at companies with LLMs and how to approach non-trivial tasks
3.
▲
Creating a better code review process
(giladpeleg.com)
1 points
by
pgilad
6y ago
|
0 comments
4.
▲
by
pgilad
8y ago
Thanks! I like your work on it. I have several ideas on how to generally improve the CSP development that I want to implement, and needed a good infrastructure for doing it: - CSP optimizations, like removing redundant fields (like a minifi
5.
▲
Show HN: A builder tool to help generate CSPs in a type-safe way
(github.com)
4 points
by
pgilad
8y ago
|
2 comments
6.
▲
Show HN: Docker Alpine Image with Java 11 (94MB)
(gist.github.com)
1 points
by
pgilad
8y ago
|
0 comments
7.
▲
Show HN: Eslint plugin to enforce proper react-redux usages
(github.com)
2 points
by
pgilad
8y ago
|
0 comments
8.
▲
Show HN: Spring Boot microservice with graphql and mongodb
(github.com)
4 points
by
pgilad
9y ago
|
1 comments
9.
▲
Show HN: JMeter JTL Parser in Go
(github.com)
1 points
by
pgilad
9y ago
|
0 comments
10.
▲
Show HN: Spring Boot microservice with mongodb
(github.com)
2 points
by
pgilad
9y ago
|
0 comments
11.
▲
Show HN: React page visibility higher order component
(github.com)
3 points
by
pgilad
10y ago
|
0 comments
12.
▲
Show HN: Vim React PropTypes Snippets
(github.com)
4 points
by
pgilad
10y ago
|
0 comments
13.
▲
by
pgilad
11y ago
Probably never. False positives is just a nice catch-phrase ;) But I don't presume to know other people's naming patterns
14.
▲
by
pgilad
11y ago
Yep, truly avoiding false positives and capturing all todos you would need to really parse the source code (perhaps creating an AST or lexical parsing). Even if you build that tool (which handles many languages) - it has an extra headache c
15.
▲
by
pgilad
11y ago
Watson looks really nice... Could definitely learn from it. In github issues you mean exporting a TODO to a github issue? If so, I don't think that belongs in Leasot, but rather an external tool for creating/manipulating Github is
16.
▲
by
pgilad
11y ago
;) I'm in no way offended. I guess kazinator is spending his time much better than me. But anyway, if anyone is more comfortable using CLI (or any IDE that provides this) with grep/ack/ag/pt and that solves parsing todos
17.
▲
by
pgilad
11y ago
This is a great solution. I would only use Leasot if you need to weed out some false positives (variable names, strings etc...) and perhaps want to output in a special format (JSON, XML, markdown...) for another tool (Think jenkins CI for e
18.
▲
by
pgilad
11y ago
Well you can see my comment above, but overall ag|awk|pt will be much faster (but might be less accurate). Leasot tries to weed out some false positive (by creating better comment for file type specific comment regexes). Also provides sever
19.
▲
by
pgilad
11y ago
Leasot is written in Node.js. Regarding pretty output - that could definitely be argued, but Leasot also allows for different reporters, say you want the output in JSON/XML for an external tool. That is extendable, whereas grep over re
20.
▲
by
pgilad
11y ago
Thanks for the comments. Regarding simple `ag` or `grep` usages: Yeah, that will definitely be faster (as with git grep). The problem arises when you have false positives due to either strings, variable names or other things (perhaps templa
21.
▲
by
pgilad
11y ago
This could actually be implemented, but it was more work with the regex so I skipped it for now, seeing that most TODOs are at the beginning of the line. Also, you run into problems with strings which might be a false positive
22.
▲
Show HN: Parse and output TODOs and FIXMEs from comments in your files
(github.com)
49 points
by
pgilad
11y ago
|
43 comments
23.
▲
Show HN: Detect which global variables are used in your jade templates
(github.com)
1 points
by
pgilad
11y ago
|
0 comments
24.
▲
Show HN: Extract your todos/fixmes from your src files
(github.com)
2 points
by
pgilad
12y ago
|
0 comments
25.
▲
Show HN: See how NPM will normalize your package.json data
(pgilad.github.io)
2 points
by
pgilad
12y ago
|
0 comments
26.
▲
Show HN: Generate a TODO.md from todos and fixmes in your code using Gulp stream
(github.com)
3 points
by
pgilad
12y ago
|
0 comments
27.
▲
by
pgilad
12y ago
I'm not aware of any linters applying this sort of logic in suggesting to extract numbers to their own declarations. One could also go as far as declaring strings and whatnot...
28.
▲
Show HN: Find numbers that should be extracted as constants in your JS
(github.com)
7 points
by
pgilad
12y ago
|
2 comments
29.
▲
Scale your css z-indexes to a sane range maintaining order
(github.com)
1 points
by
pgilad
12y ago
|
0 comments