Thank you, we'll try to review it ASAP!

Sorry for the late reply @mkm17, I totally missed your remark last time.

I noticed that retrieving the list instance, like in the getDocumentLibraryInfo function, appears in several places in the solution. Could you advise on where we should store this common code? Is spo.ts the correct file for it?

Is this something we are using at a lot of other spots? Seems like in your code you are only retrieving the list BaseType. I don't know if we need this in other places?

Similarly, for retrieving a field, should the getColumn function also be placed in spo.ts?

SPO util will be the right place I guess, yes.

Do you think I should make these updates in this PR, or would it be better to create a separate one?

To me, it kind of depends on how many places we'll have to replace code by this util function. If it's just one other command, you can easily add it to this PR. If there are like 5 other commands sharing the same logic, I'd opt for a separate issue/PR.

Hi, according to the latest comments from @martinlingstuyl on the specification, I have changed the current apply command to set.

The prompt and isEnabled parameters are optional if the selected column already has the autofill setting applied. In the update case, we can modify both of these settings.

I have used the column property AutofillInfo to check if it is an update and the _api/machinelearning/SetColumnLLMInfo endpoint to update the autofill column settings.

I noticed an issue with the test stage in the PR checks, but all tests pass when I run them locally. Can we rerun these checks without changing the code?

I noticed an issue with the test stage in the PR checks, but all tests pass when I run them locally. Can we rerun these checks without changing the code?

I just did rerun them, but it seems like it doesn't help. I think something is wrong with the macOs pipeline, in the last couple of days I saw this pipeline failing on other PRs as well. We'll have to take a look at it.

Hi @mkm17, I rebased your PR to the latest main to see if our pipeline has been fixed. I hope you don't mind if we take you as a test. Since I performed a force push, I recommend you delete your local branch and pull again from your forked repo.

Hi @milanholemans sorry for the delay. I've finally made some changes to this command. it's now ready for review.

Oh and also could you fix/rebase the branch to fix the merge conflicts? Thanks in advance!

@martinlingstuyl thank you for the review. I hope that I have covered all the suggestions.

@martinlingstuyl are you planning to push this PR forward?
This PR is blocking a follow up issue.
Let me know if you would like me to take this one over

Hi @Adam-it, I'm unable to pick it up currently, unfortunately... would you pick it up for me?

On it