[OSDEV-1779] [Backmerge] SLC. Implement correct implementation of the Parent Company field and apply snake_case keys to request payload from production location info page

[VadimKovalenkoSNF]

Backmerge fix for OSDEV-1779

1. Make Parent Company field as regular text field.
2. Convert camelCase keys to snake_case keys (e.g. location_type, number_of_workers, parent_company, processing_type and product_type) for request payload from production location info page to conform API specs.
3. Update unit tests.

[coderabbitai]

Warning

Rate limit exceeded

@VadimKovalenkoSNF has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 23 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 8a18b14 and bd7f778.

📒 Files selected for processing (1)

• src/react/src/util/util.js (3 hunks)

📝 Walkthrough

Walkthrough

This pull request updates the contribution data handling by renaming object properties and refining the data transformation logic. Test cases are revised to check for property renaming and snake_case conversion. The action dispatch functions now pass the parsed contribution data, and the ProductionLocationInfo component is modified to treat the parent company field as a simple text input rather than a selectable component. Additionally, utility functions are enhanced with new helpers to convert keys and filter empty fields in the data payload.

Changes

File(s)	Change Summary
src/react/src/tests/utils.tests.js	Renamed properties from snake_case to camelCase in test inputs and expected outputs; added a new test case to verify conversion of camelCase keys to snake_case for request payloads.
src/react/src/actions/contributeProductionLocation.js	Updated the createProductionLocation and updateProductionLocation functions to dispatch actions with the parsedContribData parameter, ensuring tracked context during creation and update processes.
src/react/src/components/Contribute/ProductionLocationInfo.jsx	Changed parentCompany state from an array to a string; replaced StyledSelect with a TextField; introduced handleParentCompanyChange to update state; simplified state initialization from singleProductionLocationData.
src/react/src/util/util.js	Restructured the parseContribData function, adding convertToSnakeFields and filterNonEmptyFields helper functions to transform object keys to snake_case and filter out empty values before constructing the payload.
doc/release/RELEASE-NOTES.md	Added a new entry in the release notes detailing the conversion of the Parent Company field to a text field and the application of snake_case keys to standard keys in the request payload.

Possibly related PRs

• [OSDEV-1397] Facilities. Avoid invoking api/parent-companies/ request on page load #473: The changes in the main PR, which involve renaming properties and modifying the handling of the parentCompany field, are related to the adjustments made in the retrieved PR that also focus on the parentCompany field, specifically its transition from a select input to a regular text input.
• [OSDEV-1130] SLC. Implement collecting contribution data page (FE) #463: The changes in the main PR, specifically the updates to the parseContribData function and the handling of the parentCompany field, are directly related to the modifications in the ProductionLocationInfo.jsx component in the retrieved PR, which also involves managing the parentCompany field and its data structure.
• [OSDEV-1748] Align SLC with current v1/production-locations validation. #520: The changes in the main PR are related to the modifications made to the parseContribData function in the retrieved PR, as both involve restructuring and enhancing the data processing within that function.

Suggested reviewers

• vladsha-dev
• roman-stolar
• mazursasha1990
• Innavin369

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[barecheck]

React App | Jest test suite - Code coverage report

Total: 29.56%

Your code coverage diff: 0.03% ▴

✅ All code changes are covered

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[barecheck]

Django App | Unittest test suite - Code coverage report

Total: 80.44%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[mazursasha1990]

LGTM

[vladsha-dev]

LGTM