That’s ok, you may find the Typescript way of doing JS is a bit more like C# though.
Plenty of C# to play with though. Had a go at porting our MongoDB based cache provider to the latest version of their API but gave up after several hours, no idea how to port our spatial queries (without resorting to native MongoDB syntax) and also retain the chained linq wheres we use for filtering results.
The most important backend areas are our API (which was originally written before rest APIs were a thing and well before MVC/web API) and our data imports (which have been neglected).
To really play with the code (and run tests etc) you need a MongoDB back and an SQL database backup which I can provide if you do decide to work on anything later.
My current goals are:
- API updates to .net core and port to Linux so we can offer an ‘easy’ self hosting mirror option
- provide a ‘good’ editor as part of the app and move all edits to that.
- implement equipment grouping in the data model (e.g. stations having one or more connectors)
- updating and add imports, move import process off the server to an external tool (may run as a process on a Linux server)
- add a geojson layer viewer to the app for data comparisons (given a data file which POIs appear to be missing, to determine if we need an import from that source).
Meanwhile I do have other projects I should be working on but currently I’m finding time for OCM that I haven’t been able to find for a few years, so that’s a good thing. Breaking the API recently highlighted just how many people are dependent on it, which is motivation in itself. CloudFlare tells me we transferred around 520GB of data last month.