You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have cloned the app, added ability to have "Context=View|Embed|Edit" appended to GET requests. This requires an addtl argument on all methods that result in GET.
Question is how would you prefer to implement?
Extending all method signatures with optional Context enum (which already exists); however this places it after CancellationToken parameter which traditionally is last parm in a method signature.
Overloading all signatures with a required first parameter of Context; this would become the code-bearing method and originals would simply invoke, passing a default Context; however the general coding philosophy seems to be to have defaulted optional parameters wherever possible.
I favour 2 - anyone have thoughts or care to vote?
Regards, Rick.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have cloned the app, added ability to have "Context=View|Embed|Edit" appended to GET requests. This requires an addtl argument on all methods that result in GET.
Question is how would you prefer to implement?
I favour 2 - anyone have thoughts or care to vote?
Regards, Rick.
Beta Was this translation helpful? Give feedback.
All reactions