Steve Ives
Currently, it appears that if you have a multi-leg query that traverses several entities via expanded relations, if you apply a $select to one entity then you must also apply...
If the data file specified in the repository is not found we currently generate an invalid response, like this: {"@odata.context":"https://localhost:8086/odata/$metadata#Cusmasas","value":[ This is a fatal error and should be causing a...
I just took an existing project that did not have authentication enabled, and used "harmonycore regen" twice, once to parse regen.bat and once to generate code. The code was generated...
The OData 4 spec states that “ To apply a PATCH or DELETE request to each member of a collection, clients append the path segment /$each to a resource path...
Because of the way that CodeGen works, GROUP fields are flattened into multiple individual fields. While this is typically OK for single groups, it can quickly become a problem in...
We should do some testing to ensure that "accented" (8-bit) characters are preserved correctly in all scenarios by Harmony Core, including: - Local OData (Windows data, no xfServer) - GET,...
Consider allowing structure-specific endpoint selection via the HarmonyCoreCustomization.json
In solutions based on the `harmonycore` project template we rely on common properties to set RPSMFIL and RPSTFIL. This is because we can't currently use project references to the repository...
It should be possible to suppress the return of OData metadata in a response by modifying the requests Accept header like this: ``` Accept: application/json; odata.metadata=none ``` or to extend...
We now generate API documentation in all services, but as soon as authentication is enabled (either OAuth or custom) the usefulness of the documentation is degraded because the "Try it...