Skip to content

docs: clarify subject-case #3638

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

Closed
4 tasks
olets opened this issue Aug 9, 2023 · 0 comments · Fixed by #3640 · May be fixed by ramzimalhas/standard-sdk-js-comake#3
Closed
4 tasks

docs: clarify subject-case #3638

olets opened this issue Aug 9, 2023 · 0 comments · Fixed by #3640 · May be fixed by ramzimalhas/standard-sdk-js-comake#3

Comments

@olets
Copy link
Contributor

olets commented Aug 9, 2023

Expected Behavior

  1. The reference-rules standard is for the condition to say that found value "is in case value".
  2. The comments in the possible values follow a standard pattern

Current Behavior

  1. subject-case docs specifies the default value's value in the condition.
  2. subject-case's "possible values" includes
    'lower-case',    // default
    
    which is an outlier compared to the rest of that code block, which uses the form
    'upper-case',    // UPPERCASE
    

Affected packages

  • cli
  • core
  • prompt
  • config-angular

Possible Solution

  1. Change subject-case's condition language
  2. Change subject-case's "possible values" to use // lower case instead of // default

Context

I was modifying my subject-case config, and needed to see what the possible options were.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants