[Concept] API Query Language LSSMAQL about lssm-v.4 HOT 7 OPEN

I just found something that would be an interesting change to this idea.
There is a query language for JSON that is perfect for our usecase and should be easy to implement.
I understand that it's not "made" by us but would provide a feature till we do.

from lssm-v.4.

Version V.0.0.1 merged into master with #53

from lssm-v.4.

I've been looking into the examples given and found one thing that is a bit weird:

sum of personal in all buildings that have more than 3 vehicles
sum((buildings WHERE len(vehicles WHERE .building_id = ..id) > 3).personal_count)

in this example, personal_count strikes me as odd.
I know that much of the LSSM is german (since the game is german), but as this is a query language, where everything is in english, I do believe that using the english personnel_count would be better suited. Especially since personal refers to something completely different in english

from lssm-v.4.

I've been looking into the examples given and found one thing that is a bit weird:

sum of personal in all buildings that have more than 3 vehicles
sum((buildings WHERE len(vehicles WHERE .building_id = ..id) > 3).personal_count)

in this example, personal_count strikes me as odd.
I know that much of the LSSM is german (since the game is german), but as this is a query language, where everything is in english, I do believe that using the english personnel_count would be better suited. Especially since personal refers to something completely different in english

Thats just a name used in the API of the game. And LSSMAQL is just something to use the APi of the game. So they need to use the exact names of that.

from lssm-v.4.

The attributes are the same as used in the APIs:
https://www.missionchief.com/api/buildings
https://www.missionchief.com/api/vehicles
https://www.missionchief.com/api/allianceinfo
https://www.missionchief.com/api/credits
https://www.missionchief.com/einsaetze.json

This is because Sebastian, the original founder of the game, used some "denglish" (mixing german and english) terms internally and the new developer team also does this now and then.

As the idea of LSSMAQL was/is to provide a Language to query these APIs, the exact same attribute names are required.
There are also plans to provide a GUI for LSSMAQL but unfortunately the project is on hold currently.

from lssm-v.4.

Possible alternatives:

• https://github.com/jmespath/jmespath.js
• https://github.com/jsonata-js/jsonata

from lssm-v.4.

after fiddling around with JSONata and GROQ in tend to favorite JSONata since a more complete feature set.
Eg. string/number conversion is not possible with groq.

from lssm-v.4.