[Cleanup] Guard remaining unguarded console.log calls
- core__crud_generic.ts: guard patch result logs (lines 246/252) with if (log_lvl) — these fired on every successful patch call - e_app_sign_in_out.svelte: already committed in previous round - element_manage_hosted_file_li.svelte: already committed in previous round All other console.log calls in launcher/lib files confirmed already guarded via $B2 context check. Remaining unguarded logs are in event handlers (fire on user action only, not hot render paths) or testing/admin pages. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -243,13 +243,13 @@ export async function update_ae_obj_id_crud_v2({
|
||||
});
|
||||
|
||||
if (!results) {
|
||||
console.log(
|
||||
if (log_lvl) console.log(
|
||||
`Not Patched - Field Name: ${field_name} with new Field Value: ${new_field_value}; Account ID: ${api_cfg.account_id}`
|
||||
);
|
||||
return false;
|
||||
}
|
||||
|
||||
console.log(`Patched - Field Name: ${field_name} with new Field Value: ${new_field_value}`);
|
||||
if (log_lvl) console.log(`Patched - Field Name: ${field_name} with new Field Value: ${new_field_value}`);
|
||||
|
||||
if (object_reload) {
|
||||
if (log_lvl) console.log(`Reloading the object after patching...`);
|
||||
|
||||
Reference in New Issue
Block a user