Skip to content

Conversation

@edwardUL99
Copy link
Contributor

@edwardUL99 edwardUL99 commented Dec 5, 2025

Summary

The parameters in the method:
procedure RequestDislikeFeedback(....,..., ContextProperties, ContextFiles)

were in the wrong order.

Moved ContextFiles to before ContextProperties

Work Item(s)

Fixes AB#615527

@edwardUL99 edwardUL99 self-assigned this Dec 5, 2025
@github-actions github-actions bot added this to the Version 27.3 milestone Dec 5, 2025
@edwardUL99 edwardUL99 linked an issue Dec 5, 2025 that may be closed by this pull request
1 task
@edwardUL99 edwardUL99 marked this pull request as ready for review December 5, 2025 13:15
@edwardUL99 edwardUL99 requested a review from a team as a code owner December 5, 2025 13:15
@edwardUL99
Copy link
Contributor Author

Not sure if 27.x is enough to be backported or are there other versions too?

Copy link
Contributor

@darjoo darjoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

darjoo
darjoo previously approved these changes Dec 10, 2025
Groenbech96
Groenbech96 previously approved these changes Dec 10, 2025
Copy link
Contributor

@Groenbech96 Groenbech96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some changes are affected by this change. Check NAV

@edwardUL99
Copy link
Contributor Author

@darjoo I wanted the dislike function to be consistent with the like function which has the correct order, but if we should leave as is, I can do that

@darjoo
Copy link
Contributor

darjoo commented Dec 10, 2025

@darjoo I wanted the dislike function to be consistent with the like function which has the correct order, but if we should leave as is, I can do that

I understand, however once an api is out, it is a breaking change, or at least semantically in this case.
We don't have any 3p usage, so that is fine. As far as I understand, it is broken even today because the parameters are swapped, so you will need to HF this and 1p/baseapp for their usages if you decide to change the api.

There is the other option, of doing the platform HF on the feedback codeunit instead of this.

@edwardUL99
Copy link
Contributor Author

@darjoo I wanted the dislike function to be consistent with the like function which has the correct order, but if we should leave as is, I can do that

I understand, however once an api is out, it is a breaking change, or at least semantically in this case. We don't have any 3p usage, so that is fine. As far as I understand, it is broken even today because the parameters are swapped, so you will need to HF this and 1p/baseapp for their usages if you decide to change the api.

There is the other option, of doing the platform HF on the feedback codeunit instead of this.

In the platform API, the parameters are all in the correct order, it's only swapped here

@edwardUL99 edwardUL99 dismissed stale reviews from Groenbech96 and darjoo via 2b10fd4 December 15, 2025 15:28
@github-actions github-actions bot modified the milestones: Version 27.3, Version 28.0 Dec 15, 2025
@edwardUL99 edwardUL99 requested a review from darjoo December 16, 2025 16:32
@JesperSchulz JesperSchulz merged commit 37c4c77 into releases/27.x Dec 17, 2025
22 checks passed
@JesperSchulz JesperSchulz deleted the private/eddylynch/fix_param_order-on-releases-27.x branch December 17, 2025 14:47
@edwardUL99
Copy link
Contributor Author

Hi @Groenbech96 if this change still affects changes in NAV, let me know and I can fix them, or else if you want to, let me know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: [27.x] Fix parameter order in Microsoft User Feedback module

6 participants