search

rbeckman-nextgen / test-mc6

0 stars 0 forks source link

Add ability to find usages of code template methods #1685

Open rbeckman-nextgen opened 4 years ago

rbeckman-nextgen commented 4 years ago

While examining or modifying a code template it would be helpful to know if/where that code template is used. A feature to 'find usages' of a particular JS method would be helpful.

Since JS is not compiled this really couldn't be done as a Java IDE would, but a simple text search within the channel XML should suffice. Just check to see if the method is called and report on what channel, transformer/filter, and step it's used in.

Imported Issue. Original Details: Jira Issue Key: MIRTH-1722 Reporter: jbartels Created: 2011-01-19T07:14:08.000-0800

rbeckman-nextgen commented 4 years ago

This should be done as part of MIRTH-1276.

Imported Comment. Original Details: Author: geraldb Created: 2011-01-19T09:25:15.000-0800

rbeckman-nextgen commented 4 years ago

Earlier today I came across a support case where a client specifically asked if a particular code template library was being used anywhere in their Mirth Connect instance. Of course, checking this manually can be potentially very time consuming, error prone, and tedious (even in cases where only a few channels exist). This feature would definitely make completing this task much easier.

Imported Comment. Original Details: Author: fuentesj Created: 2018-02-23T11:36:06.000-0800

rbeckman-nextgen commented 4 years ago

Just FYI, in 3.3 we overhauled code templates and introduced the concept of code template libraries (MIRTH-1892). I know some users still do it the "old" way where all code templates are included on all channels. That can easily lead to memory issues because a copy of each and every compiled script is included on each and every channel. One of the intents behind the changes in 3.3 is that the user would organize templates into different libraries, and then (most importantly) only include the libraries on channels that need them. Not only is it much more memory efficient, but it also allows you to easily see which channels a library is included in. Each code template can also be included only in specific contexts as well (like preprocessor, filter/transformer, source vs. destination, global scripts, etc.), further improving the memory efficiency.

Granted it's not the same as what this issue is talking about, but maybe it will help. Some work needs to be done up-front to organize libraries, limit code template contexts, and limit library-channel links. But once that is done you'll certainly benefit from a maintainability standpoint.

Imported Comment. Original Details: Author: narupley Created: 2018-02-23T11:47:26.000-0800