Skip to content

doc: fix layout of OperatorHub doc #171

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

Merged
merged 1 commit into from
Dec 1, 2021
Merged

doc: fix layout of OperatorHub doc #171

merged 1 commit into from
Dec 1, 2021

Conversation

camilamacedo86
Copy link
Contributor

@openshift-ci openshift-ci bot requested review from jmrodri and njhale November 8, 2021 22:25
// * Deep Insights
//
// * Auto Pilot
//
Copy link

Choose a reason for hiding this comment

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

+1 on this added spacing since it helps separate "capabilities" above and the "categories" below.

Copy link

@tlwu2013 tlwu2013 left a comment

Choose a reason for hiding this comment

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

I am not sure if it's just me but adding all these extra spacings makes me feel it's a bit harder to read through the comments.

I do like some extra spacings to better separate the zoning though. So perhaps the rule could be we add spacings between every - but no extra spacings between * so things are that not wide spread but still provides some zoning?

What do you think?

@camilamacedo86
Copy link
Contributor Author

Hi @tlwu2013,

I am not sure if it's just me but adding all these extra spacings makes me feel it's a bit harder to read through the comments.

The changes here are required to fix the layout for its docs to be generated properly. We ought to not ask for a look in the code and instead provide the link: https://pkg.go.dev/github.com/operator-framework/api@master/pkg/validation/internal#OperatorHubValidator

I do like some extra spacings to better separate the zoning though. So perhaps the rule could be we add spacings between every - but no extra spacings between * so things are that not wide spread but still provides some zoning?

The spaces are to allow breaking the lines in the golang docs generated for the API. adopted - instead of * will not solve this need.

@tlwu2013
Copy link

thanks for the clarification, sgtm @camilamacedo86

Copy link
Contributor

@ankitathomas ankitathomas left a comment

Choose a reason for hiding this comment

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

/lgtm

Comment on lines -26 to -30
// * "Basic Install"
// * "Seamless Upgrades"
// * "Full Lifecycle"
// * "Deep Insights"
// * "Auto Pilot"
Copy link
Contributor

Choose a reason for hiding this comment

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

indentation also works for correcting the output formatting

// - The annotations capabilities into the CSV has a valid option, which are:
//   * "Basic Install"
//   * "Seamless Upgrades"
//   * "Full Lifecycle"
//   * "Deep Insights"
//   * "Auto Pilot"

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 22, 2021
@kevinrizza
Copy link
Member

/approve

@openshift-ci
Copy link

openshift-ci bot commented Dec 1, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, kevinrizza

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 1, 2021
@openshift-merge-robot openshift-merge-robot merged commit 940ea90 into operator-framework:master Dec 1, 2021
perdasilva pushed a commit to perdasilva/api that referenced this pull request Dec 3, 2021
perdasilva pushed a commit to perdasilva/api that referenced this pull request Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants