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

Fix variable naming for [ROS] version service #8292

Merged
merged 4 commits into from
Aug 9, 2022

Conversation

jtbandes
Copy link
Contributor

@jtbandes jtbandes commented Aug 8, 2022

The version information that this service is fetching is the version for a whole repository of ROS packages which all share the same version. A repository may contain only a single package with the same name, but it may also contain multiple packages, and this badge service fetches version information based on the repo name, not the package name.

@shields-ci
Copy link

shields-ci commented Aug 8, 2022

Messages
📖 ✨ Thanks for your contribution to Shields, @jtbandes!

Generated by 🚫 dangerJS against ce36eab

@@ -43,12 +43,12 @@ const packageSchema = Joi.object({
export default class RosVersion extends GithubAuthV4Service {
static category = 'version'

static route = { base: 'ros/v', pattern: ':distro/:packageName' }
static route = { base: 'ros/v', pattern: ':distro/:repoName' }

static examples = [
{
title: 'ROS Package Index',
Copy link
Member

Choose a reason for hiding this comment

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

Given the confusion so far, as well as changing the internal terminology (var/test names, etc) shall we attempt to clarify this a bit more in the user-facing text? We could consider changing the title here to clarify that the 'unit of versioning' (for want of a better term) here is the repo not the package. The other thing we sometimes do is include a documentation key in the example (e.g:

const documentation = `
<p>
OSS Lifecycle is an initiative started by Netflix to classify open-source projects into lifecycles
and clearly identify which projects are active and which ones are retired. To enable this badge,
simply create an OSSMETADATA tagging file at the root of your GitHub repository containing a
single line similar to the following: <code>osslifecycle=active</code>. Other suggested values are
<code>osslifecycle=maintenance</code> and <code>osslifecycle=archived</code>. A working example
can be viewed on the <a href="https://github.com/Netflix/osstracker">OSS Tracker repository</a>.
</p>
`
) with some extra info that is shown to the user in the builder modal. We could use this to explain what the repoName param corresponds to in ROS-land or link to relevant documentation. I'm not 100% sure what to suggest as the platform specifics of ROS are out of my wheelhouse, but perhaps we can do a bit more to explain.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added some documentation:

image

Copy link
Member

@chris48s chris48s left a comment

Choose a reason for hiding this comment

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

nice - this looks sensible to me

@chris48s chris48s added service-badge New or updated service badge squash when passing labels Aug 9, 2022
@repo-ranger repo-ranger bot merged commit 8482985 into badges:master Aug 9, 2022
@jtbandes jtbandes deleted the jacob/ros-clarify-naming branch August 10, 2022 04:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-badge New or updated service badge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants