implementation/60980 - Define restricted extension on work package journals for query safety#18366
Conversation
05cd97c to
ebf79ea
Compare
|
Oops- forgot to update the callers. 🏃🏾 |
ebf79ea to
1b28e63
Compare
brunopagno
left a comment
There was a problem hiding this comment.
The code changes look okay to me.
I do feel it's going to be more difficult for someone to find the restricted_visible method when someone wishes to debug it, but it's a bit of the nature of rails applications.
But it seems to have broken some specs, so we need to look into those before pushing forward
fb377ac to
b6f6812
Compare
AR association extensions ensure the `restricted_visible` scope is only visible on the work package journals association. #18091 (comment)
b6f6812 to
078c326
Compare
Cheers for the review- tbf, finding the association was already hard enough- and the journalization is encapsulated in one mixin, so hopefully that and the unit tests improve the odds of working it out. Definitely open to ideas on improving this 👍🏾
yeah, I blindly enabled frozen string literals - which broke some existing string mutations that I'd rather not mess with in this PR. |
ulferts
left a comment
There was a problem hiding this comment.
Overall, I like this change @akabiru . To me, it reads nicer and appears to be more solid. Thanks for picking up my review feedback from before.
I added on point that I think could improve readability but as is the nature of such things, it is opinionated. So feel free to ignore it if you disagree.
f794f26
into
implementation/60980-introduce-work-package-restricted-comments-as-part-of-journal-notes
AR association extensions ensure the
restricted_visiblescope is only visible on the work package journals association.#18091 (comment)