fixed test csv/api mappings

[MaryKilewe]

Summary by Sourcery

Fixes issues with CSV/API mappings in the selector form. It ensures that mappings are correctly updated when a base variable is already mapped and prevents duplicate entries.

Bug Fixes:

• Fixes an issue where mappings were not correctly updated when a base variable was already mapped.
• Prevents duplicate entries in the form data.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request fixes issues with CSV/API mappings in the selector form. It updates the databaseColumns state to be an array, modifies the handleApiColumnSelect function to update existing form data entries instead of creating new ones, and modifies the handleTableSelect function to update existing form data entries instead of creating new ones.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updates the state variable databaseColumns to be an array instead of an object.	Changes the initialization of the databaseColumns state variable from {} to [].	src/pages/mapper/selector-form/CsvApiSelectorForm.js
Modifies the handleApiColumnSelect function to update existing form data entries instead of creating new ones, and ensures case-insensitive matching.	Changes the table name to '-' when a mapping exists. Changes the join_by to '-' when a mapping exists. Converts baseVariable to lowercase for case-insensitive comparison in mappingExists.	src/pages/mapper/selector-form/CsvApiSelectorForm.js
Modifies the handleTableSelect function to update existing form data entries instead of creating new ones.	Adds logic to update existing form data entries in handleTableSelect. Changes the table name to '-' when a mapping exists. Changes the column name to '-' when a mapping exists. Changes the join_by to '-' when a mapping exists.	src/pages/mapper/selector-form/CsvApiSelectorForm.js

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @MaryKilewe - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using more descriptive variable names to improve readability.
• It looks like there's some commented-out code that could be removed.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

issue (bug_risk): Potential variable naming issue in handleTableSelect.

In the handleTableSelect function, the parameter is named 'basevariable' (all lowercase), but the code later refers to 'baseVariable'. Similarly, 'column' is referenced without a defined value. This appears to be a mistake—please confirm that the correct variables (likely 'basevariable' and 'csvHeaderSelected' instead) are used to update the mapping.