-
Updated
Sep 3, 2021 - JavaScript
schema
Here are 1,652 public repositories matching this topic...
-
Updated
Aug 24, 2021 - TypeScript
-
Updated
Sep 15, 2021 - TypeScript
-
Updated
Aug 20, 2021 - TypeScript
-
Updated
Sep 13, 2021 - Python
-
Updated
Sep 13, 2021 - TypeScript
-
Updated
Aug 23, 2021 - Python
-
Updated
Sep 7, 2021 - HTML
-
Updated
Sep 4, 2021 - Go
-
Updated
Jul 23, 2021 - JavaScript
-
Updated
Jul 9, 2021 - TypeScript
-
Updated
May 11, 2021 - JavaScript
-
Updated
Mar 29, 2019 - Ruby
-
Updated
Sep 15, 2021 - TypeScript
-
Updated
Sep 13, 2021 - Java
Describe the bug
Unnecessary text explaining the project migration history maximum display count when there is no migration history at all.
Steps or screenshots to reproduce the behavior
- Go to a project where none of its database contain migration history (e.g. a new project), and click "Migration History"
- It displays a label "For database having migration history, we list up
Looks like it should be "Not all child routes satisfy compojure.api.routes/Routing."
Maybe a fix could use (str ::Routing)
or some derivative
-Victor
-
Updated
Sep 7, 2021 - TypeScript
Here is an example of current error message:
The 'email_address' field must not be empty.
Is there a way to pass field label into schema so the error message is displayed like so:
The 'Email Address' field must not be empty.
I know we can use custom messages for each field but curious if there's a lazier approach here :)
Add some validation checks for mongo operators that can't be done by SimpleSchema. See longshotlabs/meteor-simple-schema#9.
- $rename (make sure existing values for the renamed key validate for the new key name)
- $inc (check min/max and allowed values)
- $addToSet (check maxCount)
- $push (check maxCount)
- $pull (check minCount)
- $pullAll (check minCount)
- $pop (check min
Similar to the Email validator.
Describe your problem
When users run a mutator (e.g. set-annotations
), the output doesn't tell them which files changed. The only way a user can figure out which files were affected is by looking through them manually or doing git status
or however they might normally be notified of changes to files.
It would be nice if we were able to notify the user which files changed as a result
Improve this page
Add a description, image, and links to the schema topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the schema topic, visit your repo's landing page and select "manage topics."
The title might seem a bit vague but I don't know how to describe it any better tbh :-)
Anyway this is what happened: I got some 500 responses from the schema registry and all I could see in the logs was :
The logs di