It would be handy if the API explorer could link to the implementation of a method based on factors such as:
- source file; some heuristics would be required to deduce this for now, although we could conceivable enhance the method metadata supplied upon registration to more supply file name and and maybe line number
- version number, from which the relevant Git branch could be deduced
- desired target, either the Evergreen gitweb, GitHub, or both
Scroll-To-Text Fragment would be handy here to avoid having to care about tracking line items. For example, https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/src/perlmods/lib/OpenILS/Application/Trigger.pm#:~:text=sub%20create_active_events_for_object. This is currently implemented in Chrome but not Firefox, though it looks like Mozilla decided this year that they are willing to prototype adding support for it.
It would be handy if the API explorer could link to the implementation of a method based on factors such as:
Scroll-To-Text Fragment would be handy here to avoid having to care about tracking line items. For example, https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/src/perlmods/lib/OpenILS/Application/Trigger.pm#:~:text=sub%20create_active_events_for_object. This is currently implemented in Chrome but not Firefox, though it looks like Mozilla decided this year that they are willing to prototype adding support for it.