- Issue created by @Belazoth
- @belazoth opened merge request.
- Status changed to Needs review
9 months ago 11:44am 20 September 2023 - π¬π§United Kingdom Belazoth
I have made a merge request with the change that will hopefully fix this issue. This is also a patch with the same changes for those who might want to use the fix before it gets merged.
- π¬π§United Kingdom Belazoth
I have updated the patch and merge request as I noticed that even if you had the permission 'update report data' you could not update the report data as it was looking for a different permission.
- Status changed to Needs work
8 months ago 5:53pm 20 October 2023 - π¬π§United Kingdom welly
Looks pretty good to me. I would say it'd probably be preferable to inject β the AccountProxy service rather than using Drupal::currentUser but can see the module was previously using that method to get the user. The class is well set up for dependency injection so I think it might be worth doing that.
That's the only thing I would suggest, otherwise looks good.
I'll put this in "Needs work" for now - if you feel like using dependency injection for the current user/accountproxy service then please do otherwise perhaps someone else can take a look and move it to RTBC?
- Status changed to Needs review
8 months ago 4:38pm 27 October 2023 - π¬π§United Kingdom Belazoth
Thanks for the suggestion Welly. I have updated the patch and the merge request, let me know if everything you have any other suggestions.