Q: Re: Resharper string format annotations

[mwpowellhtx]

Q: for the community at large. Anyone know of the background behind the StringFormatMethodAttribute annotations? In particular concerning "plural*" arguments, pluralMsgId, pluralText, etc. There was a note there, not hundred percent certain as to its source, possibly in reference to a JetBrains Resharper issue; but is it public facing? i.e. without having to be behind any subscriber paywalls, for instance.

//< not yet supported, #1833369.

Possibly advent circa 1.2.6-alpha release.

All in all, carrying the torch forward, I am not adverse to lending credence to JetBrains Resharper support in whatever way makes sense to do so. Although today my Resharper licenses have lapsed, zero budget to consider keeping them up at the moment. If things pick up and I am able to, I do rather like the enhancements, however.

Just needing to know what this is in reference toward. i.e. "'what' is not yet supported", i.e. perhaps stacking annotations, multiple parameters, something like that, prima facie i.e. on its face, at surface level? Or something deeper, NGettext or even NGettext.Wpf related perhaps.

[mwpowellhtx]

So far, best guess is that #1833369 probably, more than likely, has to do with the AllowMultiple = false aspect in and of itself, or at least as far as Resharper is concerned.

As far as the annotations themselves are concerned, I get it, why the author might have presented those arguments as such. Perhaps there is a more contemporary System.ComponentModel way of doing that.