-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/#354 deprecation of jql search and evaluate expression endpoints #355
Conversation
`npm fix audit`
RangeError: options.minThreads and options.maxThreads must not conflict Fixed by adding `--minWorkers=8` to `test:unit` in package.json
Only implemented unit test for the newly added function evaluateJiraExpressionUsingEnhancedSearch()
Implemented new function evaluateJiraExpressionUsingEnhancedSearch()
Only implemented unit test for the newly added function evaluateJiraExpressionUsingEnhancedSearch()
Implemented new function evaluateJiraExpressionUsingEnhancedSearch()
To be honest, I was working on these same improvements in parallel, but not all the naming was done as well as you’ve done it, so I suggest merging |
…ion-of-JQL-search-and-Evaluate-expression-endpoints
Hi @MrRefactoring, I don't have a strong opinion on the naming. I just copied them from the Jira API documentation and got some inspiration from your existing code. Could you suggest some code or group that you would like me to review for the naming? Otherwise, I think it's fine 👍 |
You can start with the methods you’ve already added. After merging with the release branch, the names might get overwritten by my changes, and I’d like to preserve yours |
…ion-of-JQL-search-and-Evaluate-expression-endpoints
Fixes #354.
issueSearch
jiraExpressions