For completeness, the app is located on github here.
The app is quite dated, so mz first suggestion is to get the app back running into a current NC instance. This might mean some changes that need to be carried out.
If I understand you correctly, you want to know what API endpoints the app provides in its current state. This is defined in the routes.php file. Theoretically, this could be defined in the Controller classes as well, but the named app does not do this yet.
So, you have the endpoints /apps/customproperties/customproperties
(using GET, POST, and PUT) as well as /apps/customproperties/customproperties/{id}
(as DELETE with a value for {id}
).
For more analysis, I would have to dig into stuff. First, you should tell us, what you actuall know and what you need to prevent unneeded work.
OK, this is not necessarily related to the APIs provided by the app. You should be able to keep that API stable as far as I guess (without prior checks) and directly fix any inconsistencies with the current NC server.
A quick glance shows that there are not too many tests existing. So, you will have to manually check thoroughly.
I have taken over an app as well and it was quite some work to get this done. Best is if you could get in touch with the original author to hand over the app formally. Otherwise, I am not sure if there is an actual process on the side of NC (to be able to publish to the app store). So, it is easier if you had the agreement by @SteKoe.
Did you try it on the current NC version, yet? Just to see if it generally loads or not. Then, you could see if it works in general.
Some more ides/hints:
- Enable debug mode.
- Increase verbosity as much as possible.
- Use a dedicated development environment.
- Have a debugger ready to use
- Do not try to get everything running in one big step.
- Mainly look for the currently supported NC server versions.