"not valid" constraints don't show up in schema.md

Open
#4,063 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
databases

Research direction

Start by comparing the missing "not valid" constraints in db/schema.md with the related behavior described in #3987. Find the regex mentioned in the issue and trace how it determines which constraints are written to the schema file. Done means the relevant "not valid" constraints appear in db/schema.md.

Written by the indexing model from the issue text.

Description

See #3987 - the "not valid" constraint doesn't seem to show up in db/schema.md. This is probably a matter of adding "not valid" to a regex somewhere.

Dominant language
JavaScript
Stars
435
Forks
305
Avg merge
1d 9h
Merged PRs (30d)
93

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from taskcluster/taskcluster

All issues in taskcluster/taskcluster

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.