Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential issue #1214

Closed
symbiogenesis opened this issue Jul 7, 2024 · 1 comment
Closed

Potential issue #1214

symbiogenesis opened this issue Jul 7, 2024 · 1 comment

Comments

@symbiogenesis
Copy link
Contributor

symbiogenesis commented Jul 7, 2024

I was looking at the analyzers around CA1507 and RCS1015 and I noticed the following code:

// Set the sync_row_timestamp
// glitch in delete metadata command
var syncSyncRowTimestamp = syncAdapter.GetParameter(context, command, "sync_row_timestamp");
if (syncSyncRowTimestamp != null)
syncAdapter.AddCommandParameterValue(context, syncSyncRowTimestamp, sync_min_timestamp.HasValue ? sync_min_timestamp.Value : DBNull.Value, command, commandType);

All of the other added command parameters in this function have matching variables to the string literal, and could actually be improved by converting them to use nameof().

Except this one.

On this one the string literal is "sync_row_timestamp" but there is no corresponding variable by that name, and the value being passed on line 189 is actually sync_min_timestamp

This has a comment about a glitch, so maybe it is intentional. Or, maybe this is why there is a glitch. I'm not sure.

@Mimetis
Copy link
Owner

Mimetis commented Aug 22, 2024

Yes, this is just an historical mistake I've made in older versions that I still not fixed (coz it's working :) )
Will make a fix sooner or later :D

@Mimetis Mimetis closed this as completed Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants