Re:Jschema.js is a framework for modeling data in JavaScript
by ignoreintuition on Saturday November 04, 2017 @10:40PM
(#15627918)
Reading through some of these comments I agree: It is probably a good idea to add in a 'why to use' section on the repo. The purpose behind this was that I found it cumbersome to work with dataets in JavaScript so this framework lets you pull them into a schema that has metadata to handle relationships between tables, aggregation methods, sorting and filtering. As for competing frameworks: I have seen some of this in other larger frameworks but I build this out so I can work with data in JS without pulling in monolithic data visualization libraries.
Re:Jschema.js is a framework for modeling data in JavaScript
by eoincathal on Tuesday November 07, 2017 @06:49AM
(#15642580)
I can see a use case in my current work. We're building a dashboard visualisation for our product.
I'm writing the REST API backend for it - and trying to make that API as easy to easy to use for the front end (inhouse customer) as I can. However, I'm finding that I'm writing a lot of endpoints that are variations on the same data.
We will circle around, identify the common patterns/variations and consolidate a bunch of the code. But something like this, that facilitates sorting, grouping and filtering on the front end, could be useful.
What is this for? Talking to a REST API? Serializing and de-serializing data? Acting as an in-memory DB? What library does it compete with?
I'm writing the REST API backend for it - and trying to make that API as easy to easy to use for the front end (inhouse customer) as I can. However, I'm finding that I'm writing a lot of endpoints that are variations on the same data.
We will circle around, identify the common patterns/variations and consolidate a bunch of the code. But something like this, that facilitates sorting, grouping and filtering on the front end, could be useful.