docs: improve JSDoc of allowEval properties

[tbouffard]

Highlight with a warning that enabling eval carries a possible security risk.

Notes

Covers #722

Summary by CodeRabbit

• Documentation
  • Revised in-app guidance and warnings to improve clarity and consistency, helping users better understand potential security risks associated with dynamic evaluation.
• New Features
  • Enhanced configurability within the graph display settings by introducing controls that allow users to check and update evaluation options more intuitively.

[coderabbitai]

Walkthrough

This pull request updates documentation and comments across several modules for improved clarity and consistency. In the core serialization files, phrasing in comments and code examples is corrected. The static property related to executing code via the allowEval flag receives enhanced warning notes in both the stylesheet and node configuration files to highlight potential security risks. In addition, the GraphView class now provides explicit getter and setter methods for managing the allowEval property along with an expanded comment explaining its behavior. These changes do not alter functionality but improve readability and developer guidance.

Changes

Files	Change Summary
packages/core/src/serialization/ObjectCodec.ts, packages/core/src/serialization/codecs/StylesheetCodec.ts, packages/core/src/view/geometry/node/StencilShape.ts	Updated comments and code examples to correct phrasing (e.g., "look up" instead of "lookup", "field names" instead of "fieldnames"). Added warning notes regarding the security risks of enabling the allowEval switch.
packages/core/src/view/GraphView.ts	Enhanced the allowEval property documentation with detailed explanations and warnings. Added new methods: isAllowEval() (getter) and setAllowEval(value: boolean) (setter) for managing the property.

---

📜 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 86b3d18 and af816a6.

📒 Files selected for processing (4)

• packages/core/src/serialization/ObjectCodec.ts (5 hunks)
• packages/core/src/serialization/codecs/StylesheetCodec.ts (1 hunks)
• packages/core/src/view/GraphView.ts (2 hunks)
• packages/core/src/view/geometry/node/StencilShape.ts (1 hunks)

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

• GitHub Check: build (windows-2022)

🔇 Additional comments (7)

packages/core/src/view/geometry/node/StencilShape.ts (1)

46-49: Good security improvement in the documentation

Adding this explicit warning about the security risks of enabling allowEval is an important improvement to the documentation. This helps developers make informed decisions about the potential security implications of their configuration choices.

packages/core/src/serialization/codecs/StylesheetCodec.ts (1)

41-43: Good security warning addition

Adding the warning about security risks when enabling allowEval is important for helping developers understand the potential implications of this configuration option. This is particularly important since this property defaults to true.

packages/core/src/serialization/ObjectCodec.ts (3)

224-225: Enhanced security warning for allowEval

Good improvement changing "NOTE" to "WARNING" and adding the explicit message about security risks. This provides clearer guidance to developers about the potential implications of enabling this feature.

---

138-139: Grammar fix: "look up" instead of "lookup"

Good correction of the verb form "look up" which is the proper form in this context.

---

176-181: Improved code example formatting

The updates to the code example with proper formatting and reference to ALIGN.LEFT instead of constants.ALIGN.LEFT make the documentation more consistent and accurate.

packages/core/src/view/GraphView.ts (2)

135-141: Enhanced documentation for allowEval property

The expanded JSDoc now clearly explains when and how the allowEval property is used, and importantly includes a security warning. This clarification is valuable for developers who need to understand the implications of enabling this property.

---

287-299: Added accessor methods for allowEval

Adding proper getter and setter methods for the allowEval property improves the API design by providing a consistent interface for accessing and modifying this security-sensitive setting.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

[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