Skip to content

Conversation

@yoav-el-certora
Copy link
Contributor

Naming convention:

  • PRs for features that are in design should have the "proposal" label
  • PRs for features that haven't landed yet should have the "future" label
  • PRs for upcoming releases should have the "release" label
  • PRs with new documentation for existing features should have the "existing feature" label

Before requesting review:

  • Make sure there is a ticket in the DOC board in Jira
  • Make sure CI is passing
    • Spell check failure may require adding backticks around code or updating spelling_wordlist.txt
    • See README.md for information about style and markdown syntax
    • If the CI Details link gives a 404, you need to log in to readthedocs.com
  • Add link to generated documentation here
    • you can find this by following the read the docs link from the CI check
  • Ask for help in #documentation

Jira ticket: TODO
Link to generated documentation: TODO

- [feat] Report links generated by the CLI are private by default; use `"url_visibility": "public"` to share publicly. In CI runs, links remain public by default.
- [feat] Foundry remappings support: when `packages` is not set, the tool uses `forge remappings` to resolve package mappings from `foundry.toml`.
- [deprecation] Deprecated CLI options have been removed; update configuration files to use supported alternatives listed in the CLI options docs.
- The full list is as follows: • auto_nondet_difficult_internal_funcs • auto_nondet_minimal_difficulty • contract_compiler_skip_severe_warning_as_error • send_only • use_memory_safe_autofinders • disable_finder_friendly_optimizer • do_not_use_memory_safe_autofinders • finder_friendly_optimizer • assert_contracts • allow_solidity_calls_in_quantifiers
Copy link
Contributor

@srunquist-certora srunquist-certora Sep 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To help the users and reduce support questions, would it make sense to present these as a table with columns "Deprecated Option" and "Suggested Alternative"?
E.g. for allow_solidity_calls_in_quantifiers, could say "Use direct storage access if possible". Some may be "None" or "N/A".

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I support Shane's idea. Also, wrap the option names in code quotes to make them look nicer and so that the spell checker will know to ignore them.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tbh I don't really know how to add a table in those .md files.
Can I provide the "Suggested Alternative" and either one of you help here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

- [feat] Report links generated by the CLI are private by default; use `"url_visibility": "public"` to share publicly. In CI runs, links remain public by default.
- [feat] Foundry remappings support: when `packages` is not set, the tool uses `forge remappings` to resolve package mappings from `foundry.toml`.
- [deprecation] Deprecated CLI options have been removed; update configuration files to use supported alternatives listed in the CLI options docs.
- The full list is as follows: • auto_nondet_difficult_internal_funcs • auto_nondet_minimal_difficulty • contract_compiler_skip_severe_warning_as_error • send_only • use_memory_safe_autofinders • disable_finder_friendly_optimizer • do_not_use_memory_safe_autofinders • finder_friendly_optimizer • assert_contracts • allow_solidity_calls_in_quantifiers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I support Shane's idea. Also, wrap the option names in code quotes to make them look nicer and so that the spell checker will know to ignore them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants