#17662 [bug] add setters to LengthTokenilter

[nokternol]

The simplest approach to fixing the defect and it's the one used by all the other filter class with non-IList properties

[ghost]

Thank you for your contribution nokternol! We will review the pull request and get back to you soon.

[nokternol]

Looks like I need to kick off some code generation process from Powershell.
Not sure where that is and it's unlikely I'll have permissions to the resources required to run it.
Apologies, I was just trying to be helpful.

[ghost]

All CLA requirements met.

[nokternol]

I ran Export-API.ps1 it created the gen code I believe the analyzer is complaining about.
However, it also created the below file
sdk\mixedreality\Azure.MixedReality.Authentication\api\Azure.MixedReality.Authentication.netstandard2.0.cs
Which it feels is unrelated.

Pushed the change to the generated file but omitted the mixedreality as this feels related to other work.

[jsquire]

Hi @nokternol. Thank you, again, for your interest in helping to improve the Azure SDK experience and for your contribution. I've routed this to the team members best able to assist with review and guidance. Please be aware that due to the holidays, responses may be delayed.

[heaths]

Thank you for your contribution and catching this error! The model properties are indeed read/write. This will be in the next release, though I'm not sure exactly when that will be. cc @tg-msft @brjohnstmsft

If you need it sooner than later, please let us know.

[nokternol]

@heaths @tg-msft @brjohnstmsft I am indeed waiting for this bug fix in order to roll out a production solution so the sooner this fix is available the better.
Everything else is done and my solution is now holding up other business projects.
I appreciate that I cannot influence your timeline but it would be very helpful if I could know when the next beta build is scheduled for

[AlexGhiondea]

@nokternol we should release a new version in early February -- would that work?

[nokternol]

@AlexGhiondea I would need to check but for now I have broken of the functionality that relies on this code into a separate work item so I can process the rest. So that gives us a bit more freedom.

[nokternol]

Apologies for my lack of knowledge of on how GitHub links things.
It says my commit is not part of any branch on this repo which I'm assuming means it was squash merged and then the branch deleted.
@AlexGhiondea @annelo-msft How do I then find out what release sdk (nuget version) this fix is contained in so I can upgrade our dependencies?

UPDATE: I found the answer, clicking the 3 dots on the commit opens all tags associated which shows this commit was included in the 11.2.0 official release tag. Thank you