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

config.json: populate tags #287

Merged
merged 1 commit into from
Feb 20, 2021
Merged

config.json: populate tags #287

merged 1 commit into from
Feb 20, 2021

Conversation

ee7
Copy link
Member

@ee7 ee7 commented Feb 20, 2021

This deliberately omits some tags that we could conceivably add, such as:

  • 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 the spec.

Closes: #271

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 merged commit e97773b into exercism:main Feb 20, 2021
@ee7 ee7 deleted the config-populate-tags branch February 20, 2021 15:59
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.

[v3] Add tags
1 participant