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

feat(graindoc)!: Add --current-version flag, required for since/history attributes #1116

Merged
merged 3 commits into from
Feb 3, 2022

Conversation

phated
Copy link
Member

@phated phated commented Jan 22, 2022

Closes #1110

This adds a --current-version flag to the grain doc command line. If your docs are using @since or @history, this flag is required (thus breaking) because we need (want?) a version to compare so we can insert next into the generated markdown if the docs are being generated before a release is made.

@phated phated requested a review from a team January 22, 2022 19:28
@phated phated self-assigned this Jan 22, 2022
Copy link
Member

@ospencer ospencer left a comment

Choose a reason for hiding this comment

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

Looks great!

@phated phated changed the title feat(graindoc)!: Add --current-version flag, required for since/history attributes feat(graindoc)!: Add --current-version flag, required for since/history attributes Jan 22, 2022
@@ -11,6 +11,27 @@ type t = {
attributes: list(Comments.Attribute.t),
};

exception
MissingFlag({
Copy link
Member

Choose a reason for hiding this comment

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

I'm a bit confused -- why do we require the flag? Can we not infer a default from the compiler version?

Copy link
Member Author

Choose a reason for hiding this comment

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

Compiler version doesn't work when external libraries authors are using Grain doc. Their @since and @history will be specific to their development workflows and library version.

@ospencer
Copy link
Member

Maybe we'll be able to do something fun in the future with the Silo.toml file version!

Copy link
Member

@peblair peblair left a comment

Choose a reason for hiding this comment

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

Looks good!

Copy link
Member

@marcusroberts marcusroberts left a comment

Choose a reason for hiding this comment

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

LGTM!

@phated phated merged commit 0f681ea into main Feb 3, 2022
@phated phated deleted the phated/graindoc-current-version-flag branch February 3, 2022 19:25
@github-actions github-actions bot mentioned this pull request Feb 3, 2022
@github-actions github-actions bot mentioned this pull request May 16, 2022
@github-actions github-actions bot mentioned this pull request May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Graindoc: Add required --current-version flag instead of using grain version
4 participants