<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="text-align:left; direction:ltr;"><div>Hi Tiago,</div><div><br></div><div>That support was adding in <a href="https://reviews.llvm.org/rGfcf7cc268fe4560bc7cd751494beceff45f5dd10">https://reviews.llvm.org/rGfcf7cc268fe4560bc7cd751494beceff45f5dd10</a>. You can call `Options.get("Name")` or `Options.get<Inttype>("Name")` and it will return `llvm::Expected<...>`.</div><div>If there is no option found in the config it will return a `MissingOptionError`, If there is an option but it couldnt't be parsed to the Type it will return a `UnparseableIntegerOptionError`. you can just log the Error straight to `llvm::errs()`.</div><div><br></div><div>Regards,</div><div><br></div><div>Nathan James</div><div><br></div><div><br></div><div>On Thu, 2020-04-09 at 12:12 -0700, Tiago Macarios via cfe-dev wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>Is there a way/pattern for a clang-tidy check to require an argument (ie an entry in the .clang-tidy file)?</div><div><br>Looking at the API It has a way for me to
storeOptions, but Options.store will always have a Default value.</div><div><br></div><div>Tiago</div></div>
<pre>_______________________________________________</pre><pre>cfe-dev mailing list</pre><pre><a href="mailto:cfe-dev@lists.llvm.org">cfe-dev@lists.llvm.org</a></pre><pre><a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a></pre><pre><br></pre></blockquote></body></html>