During library development, force_build will always true

[satoren]

Summary by CodeRabbit

• Chores
  • Updated build configuration to ensure consistent build processing during testing.
  • Introduced environment variable controls for flexible build behavior management.

[coderabbitai]

Walkthrough

This pull request modifies the configuration for the rustler_precompiled application. It updates the configuration file to import the Config module and sets a fixed build option for testing. In the related library file, the logic for determining the force_build option is refactored to conditionally use an environment variable, replacing the previous direct assignment.

Changes

File(s)	Change Summary
config/config.exs	Added an import statement for the Config module and introduced a configuration setting, setting :force_build with y_ex: true for rustler_precompiled.
lib/nif.ex	Introduced a new variable that conditionally sets the force_build option based on the environment variable RUSTLER_PRECOMPILATION_YEX_BUILD, replacing the prior direct assignment.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dcd395f and 9fe5aa6.

📒 Files selected for processing (2)

• config/config.exs (1 hunks)
• lib/nif.ex (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• config/config.exs

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: lint

🔇 Additional comments (2)

lib/nif.ex (2)

7-12: Align implementation with PR objective.

The current implementation makes force_build conditional based on an environment variable, but according to the PR title, force_build should always be true during library development.

Consider simplifying to:

-force_build =
-  if System.get_env("RUSTLER_PRECOMPILATION_YEX_BUILD") != nil do
-    [force_build: System.get_env("RUSTLER_PRECOMPILATION_YEX_BUILD") in ["1", "true"]]
-  else
-    []
-  end
+force_build = [force_build: true]

---

14-20: LGTM!

The RustlerPrecompiled configuration is well-structured and correctly uses the project version for consistency.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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.

[coveralls]

coverage: 96.421%. remained the same
when pulling 9fe5aa6 on config
into dcd395f on main.