jviotti

16 ms·

151.
The SDK to make Resin.io powered JavaScript applications(github.com)
5 points by jviotti 11y ago|0 comments
152.
The feelings of a developer with a business idea(medium.com)
2 points by jviotti 11y ago|0 comments
153.
by jviotti 11y ago
Haha definitely! You could write a small module that compiles the lisp-like syntax that you mention above to a Queryl object.
154.
by jviotti 11y ago
Hey there, Objects (or DSL) are easier to encode/decode than functions. Also notice that Queryl is a very low level way of defining queries, and can easily become horrifying and unmaintainable with very complex queries. The idea was to
155.
by jviotti 11y ago
Yeah, it was inspired by MongoDB, but then deviates in some ways: - Conjunction and disjunction operations are defined by arrays in MongoDB, but as Objects in Queryl. For example: { $or: [ { foo: { $gt: 100 } }, { bar: { $gt: 200 } } ]
156.
by jviotti 11y ago
Hey there! Your second example was the original idea when building Queryl, however that required me to always inspect the properties of an object, and based on the key, check if it is a Queryl operation (e.g: starts with $ and it's rec
157.
by jviotti 11y ago
Looks cool, I haven't heard of it. However I don't think I could use their querying language separately from the ORM. Our use case for Queryl is to filter array of objects based on different criteria, but I guess an extra benefit
158.
by jviotti 11y ago
The project heavily relies on lodash for it's implementation actually, so you can of course do it straight with lodash, however the benefit is that you don't have to write any code to produce complex searches (with multiple nested
159.
JavaScript query language to perform complex object searches(github.com)
52 points by jviotti 11y ago|21 comments
160.
IssueTrack, GTD + GitHub issues(issuetrack.io)
1 points by jviotti 11y ago|0 comments