-
Notifications
You must be signed in to change notification settings - Fork 243
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
Custom patterns with Talismanrc for CLI/scanner not working #274
Comments
This is currently a known/expected behaviour. |
Thanks for confirming. Any ETA for the fix? |
@varaamo : would you be able to submit a PR for the same ? |
I'm not that familiar with the code base nor the go programing language that it is written in, to make/suggest changes to support this capability |
@svishwanath-tw, will you able to help implement this feature? |
@varaamo : I will give it a try. What do you have in mind when you say help ? |
implement and release a version that we can download and use :-) |
Thank you @svishwanath-tw |
@varaamo : The implementation is far from complete FYI. This is just a draft. Far from release. Would you be willing to do some testing and give feedback on these changes ? |
@svishwanath-tw , Yes I can test and provide feedback after you provide the talisman cli binaries when ready |
@varaamo : Can you try out with binaries available at https://github.com/thoughtworks/talisman/releases/tag/scanwithrc |
@svishwanath-tw, do i need to build the source code for the binaries? It would be easier if you can upload the binaries directly |
@varaamo : That link has binaries now. Please download and use. |
Thank you. I was able to test and it is working for me. I tested with the following custom patterns in .talismanrc and the scan was able to correctly identify them within the test file I'd created
|
Glad to know that this is working. |
Thanks for the FYI @svishwanath-tw . Any idea when these changes would be available in the main release? |
In the scan mode, it appears talismanrc with custom configuration is not been read.
So all the custom regex in the talismarc is not processed by the talisman CLI. However Talisman pre-push hook is able to read and process fine.
The text was updated successfully, but these errors were encountered: