Skip to content

RNET-1161: Implement support for using a log level for a specific log category #294

RNET-1161: Implement support for using a log level for a specific log category

RNET-1161: Implement support for using a log level for a specific log category #294

GitHub Actions / Verify TODOs failed Jun 26, 2024 in 0s

Verify TODOs

Found 12 TODO entries that don't have a link to a Github issue/Jira ticket.

Annotations

Check warning on line 66 in Realm/Realm/Handles/SharedRealmHandle.cs

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

Realm/Realm/Handles/SharedRealmHandle.cs#L66

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Update arg order to be the same across the SDK.

Check warning on line 25 in Realm/Realm/Logging/LogCategory.cs

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

Realm/Realm/Logging/LogCategory.cs#L25

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Remove 'abstract' and use this class instead of 'LeafLogCategory'?

Check warning on line 66 in Realm/Realm/Logging/LogCategory.cs

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

Realm/Realm/Logging/LogCategory.cs#L66

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Passing entire category name path for now, can update later to

Check warning on line 38 in Realm/Realm/Logging/Logger.cs

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

Realm/Realm/Logging/Logger.cs#L38

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Use this default log level?

Check warning on line 80 in Realm/Realm/Logging/Logger.cs

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

Realm/Realm/Logging/Logger.cs#L80

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Deprecate

Check warning on line 105 in Realm/Realm/Logging/Logger.cs

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

Realm/Realm/Logging/Logger.cs#L105

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Do we want to deprecate the getter as well?

Check warning on line 107 in Realm/Realm/Logging/Logger.cs

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

Realm/Realm/Logging/Logger.cs#L107

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Deprecate and refer to `SetLogLevel`.

Check warning on line 121 in Realm/Realm/Logging/Logger.cs

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

Realm/Realm/Logging/Logger.cs#L121

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Perhaps we should grab the current category (`_logCategory`)

Check warning on line 135 in Realm/Realm/Logging/Logger.cs

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

Realm/Realm/Logging/Logger.cs#L135

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Would it make sense to also deprecate the Default setter

Check warning on line 51 in wrappers/src/shared_realm_cs.cpp

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

wrappers/src/shared_realm_cs.cpp#L51

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Update arg order to be the same across the SDK.

Check warning on line 301 in wrappers/src/shared_realm_cs.cpp

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

wrappers/src/shared_realm_cs.cpp#L301

TODO entry doesn't have a link to Github issue or Jira ticket
lj): Usage in Core:

Check warning on line 305 in wrappers/src/shared_realm_cs.cpp

See this annotation in the file changed.

@github-actions github-actions / Verify TODOs

wrappers/src/shared_realm_cs.cpp#L305

TODO entry doesn't have a link to Github issue or Jira ticket
lj): But this seems to work as well: