First try to export the api keys directly from the firmware#222
First try to export the api keys directly from the firmware#2220xFEEDC0DE64 wants to merge 1 commit intomainfrom
Conversation
|
Take GitHub docu and merge it into Firmware? Use Firmware as single source for docu export? |
|
Yes but this is a very time consuming task, will see when I can do this |
|
Also the firmware doesnt have german descriptions at all |
|
I see your point and know problems like this from my day time job ;-) Manually merging is a pain and once you are done, it is outdated 3 weeks later. Sorry for doing stupid proposals , but just my 2 cents:
Sry, I know it is your firmware, we can't contribute, just making obvious comments. :-) |
e3163e0 to
049ba7d
Compare
|
firmware docs export recreated, this time I tried to keep the colum widths identical and implemented the type column too, but sometimes the getter has a different type than the setter. I have to find a solution for this, but for future reference this new export might be helpful |
049ba7d to
39aab9e
Compare
39aab9e to
d47ceee
Compare
I have added a mechanism to export the api docs directly from our firmware, and of course it differs between different hardware generations v3, v4, v5,
and I think on github there is sometimes additional information on specific api keys, better documented than the description coming from the firmware.
we have to check, that we dont eliminate any good docs from github by overwriting the texts from the firmware
This new api docs list can be browsed here:
https://github.com/goecharger/go-eCharger-API-v2/blob/export_api_docs_from_firmware/apikeys-en.md