Misc fixes

[mdellabitta]

Important

Update email in SQL script and rename field in Elasticsearch script.

• SQL Script:
  • Update email value in db-scripts/01-api-key.sql from foo@bar.com to foo@example.com.
• Elasticsearch Script:
  • Rename field ipfs to filecoin in es-scripts/init-indices.sh within the Elasticsearch index mapping.

^{This description was created by for bb0aa13. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to 5d794a9 in 1 minute and 23 seconds. Click for details.

• Reviewed 28 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. db-scripts/01-api-key.sql:5

• Draft comment:
  The email field is now set to ('' || ''), which is an unnecessarily complex way to represent an empty string. Consider using '' directly and ensure this is the intended value.
• Reason this comment was not posted:
  Marked as duplicate.

2. es-scripts/init-indices.sh:157

• Draft comment:
  The key renamed from 'ipfs' to 'filecoin'. Confirm that this change is intentional and that all dependent code is updated accordingly.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 50% <= threshold 50% The comment asks for confirmation of an intentional change, which is allowed. However, it also asks to ensure that all dependent code is updated, which violates the rules. The comment is partially useful but needs modification to comply with the rules.

Workflow ID: wflow_KUVv7iNvEwIippqJ

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed bb0aa13 in 45 seconds. Click for details.

• Reviewed 15 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. db-scripts/01-api-key.sql:5

• Draft comment:
  Good clean-up of SQL. Confirm that 'foo@example.com' is the intended email value.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to confirm their intention regarding the email value, which violates the rule against asking for confirmation of intention.

2. db-scripts/01-api-key.sql:5

• Draft comment:
  Consider appending a trailing newline for POSIX compatibility.
• Reason this comment was not posted:
  Comment was on unchanged code.

Workflow ID: wflow_tay10xK6sZG4tZty

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}