Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export generator and docs api in the pest_generator trait #961

Merged
merged 2 commits into from
Jan 6, 2024

Conversation

marcfir
Copy link
Contributor

@marcfir marcfir commented Jan 4, 2024

What it does

This PR exposes the docs module and the generator module of the pest_generator trait.
I added the missing docs for the newly exported functions, structs and modules.

Background

We are currently working on a language workbench in rust based on pest. So far we have used a separate derive macro by. But it turns out that it is easier if we do our own preprocessing of the derive attributes and just generate the parser in our own derive macro with the pest_generaotr::generator::generate function.

Improvements

We can add a feature flag as this API was not intended to be semver sensitive.

Signed-off-by: marcfir <72923599+marcfir@users.noreply.github.com>
@marcfir marcfir requested a review from a team as a code owner January 4, 2024 21:04
@marcfir marcfir requested review from NoahTheDuke and removed request for a team January 4, 2024 21:04
Copy link
Contributor

coderabbitai bot commented Jan 4, 2024

Important

Auto Review Skipped

Auto reviews are limited to the following labels: pr. Please add one of these labels to enable auto reviews.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

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

Tips

Chat

There are 3 ways to chat with CodeRabbit's AI:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
  • 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 tests 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 generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid.
    • @coderabbitai read the files in the src/scheduler package and generate README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Copy link
Contributor

@tomtau tomtau left a comment

Choose a reason for hiding this comment

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

Yeah, I think these types are internal and were not meant to be exported in public API. Maybe we can add a feature flag, e.g. "export-internal", to expose them?

Comment on lines 35 to 36
pub mod docs;
pub mod generator;
Copy link
Contributor

Choose a reason for hiding this comment

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

this can be feature-guarded

Comment on lines 122 to 131
struct ParsedDerive {
pub(crate) name: Ident,
pub(crate) generics: Generics,
pub(crate) non_exhaustive: bool,
/// Parsed information of the derive and the attributes.
pub struct ParsedDerive {
/// The identifier of the deriving struct, union, or enum.
pub name: Ident,
/// The generics of the deriving struct, union, or enum.
pub generics: Generics,
/// Indicates whether the 'non_exhaustive' attribute is added to the 'Rule' enum.
pub non_exhaustive: bool,
}
Copy link
Contributor

Choose a reason for hiding this comment

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

and this can be feature guarded -- perhaps it can be moved to some child module and here, the feature-guard would be pub use vs pub(crate) use?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

From my point of view, a child module is a good approach. I will add a commit with the feature guard and module.

* Make internal API public with the `export-internal` feature.
* Move the parse_derive functions and types to a new `parse_derive module.

Signed-off-by: marcfir <72923599+marcfir@users.noreply.github.com>
@marcfir marcfir requested a review from tomtau January 5, 2024 12:44
@marcfir
Copy link
Contributor Author

marcfir commented Jan 5, 2024

Thanks for the quick review! I have added your comments. Do you have any other suggestions?

Copy link
Contributor

@tomtau tomtau left a comment

Choose a reason for hiding this comment

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

LGTM

}
_ => panic!("grammar attribute must be a string"),
},
_ => panic!("grammar attribute must be of the form `grammar = \"...\"`"),
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: this line isn't covered by tests, but it was like that before

@tomtau tomtau merged commit 199f594 into pest-parser:master Jan 6, 2024
9 checks passed
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.

2 participants