Closed bhillkeyfactor closed 7 months ago
@fiddlermikey - We need this fixed in version 2.1 as well. Not sure how you want to handle this. Do you want to try to merge it into there from this codebase or do you want me to fix separately?
@bhillkeyfactor - We should be able to create a new PR into the 2.1 branch. It is likely there will be a merge conflict to resolve
Superseded by #26
@ITodorinski @catharinerogovin - This build should fix the issue once approved. You can have the client try the RC build to see if it works.