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

[v3] Add tags #271

Closed
Tracked by #278
ErikSchierboom opened this issue Jan 29, 2021 · 0 comments · Fixed by #287
Closed
Tracked by #278

[v3] Add tags #271

ErikSchierboom opened this issue Jan 29, 2021 · 0 comments · Fixed by #287

Comments

@ErikSchierboom
Copy link
Member

This issue is part of the migration to v3. You can read full details about the various changes here.

In Exercism v3, tracks can be annotated with tags. This allows searching for tracks with a certain tag combination, making it easy for students to find an interesting track to join.

Tags are specified in the top-level "tags" field in the track's config.json file and are defined as an array of strings, as specified in the spec.

Goal

The "tags" field in the config.json file should be updated to contain the tags that are relevant to this track. The list of tags that can be used is listed in the spec.

Example

{
  "tags": [
    "runtime/jvm",
    "platform/windows",
    "platform/linux",
    "paradigm/declarative",
    "paradigm/functional",
    "paradigm/object_oriented"
  ]
}

Tracking

exercism/v3-launch#1

ee7 added a commit to ee7/exercism-nim that referenced this issue Feb 20, 2021
This deliberately omits some tags that we could conceivably add, e.g.:
- paradigm/functional
- paradigm/object_oriented
- execution_mode/interpreted
- platform/ios
- platform/android
- runtime/language_specific

The spec currently contains:
> Tracks can be annotated with tags, which allows searching for tracks
> with a certain tag combination.

> A track should choose their tags based on the general usage of their
> language. For example, imagine a student thinking: "I'd like to do
> machine learning, what language should I pick?", or "I'd like to learn
> functional programming, which language should I choose?". If your
> language would be a good candidate, give it that tag. If your language
> supports some functional ideas but they're rarely used, or a few
> people do Machine Learning in it, but it's rare, then do not apply
> those tags.

See:
- https://github.com/exercism/docs/blob/main/anatomy/tracks/config-json.md#tags

Closes: exercism#271
@ee7 ee7 closed this as completed in #287 Feb 20, 2021
ee7 added a commit that referenced this issue Feb 20, 2021
This deliberately omits some tags that we could conceivably add, e.g.:
- paradigm/functional
- paradigm/object_oriented
- execution_mode/interpreted
- platform/ios
- platform/android
- runtime/language_specific

The spec currently contains:
> Tracks can be annotated with tags, which allows searching for tracks
> with a certain tag combination.

> A track should choose their tags based on the general usage of their
> language. For example, imagine a student thinking: "I'd like to do
> machine learning, what language should I pick?", or "I'd like to learn
> functional programming, which language should I choose?". If your
> language would be a good candidate, give it that tag. If your language
> supports some functional ideas but they're rarely used, or a few
> people do Machine Learning in it, but it's rare, then do not apply
> those tags.

See:
- https://github.com/exercism/docs/blob/main/anatomy/tracks/config-json.md#tags

Closes: #271
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 a pull request may close this issue.

1 participant