Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refuse Float and Double data values that overflow to infinity [patch] #360
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
Uh oh!
There was an error while loading. Please reload this page.
Refuse Float and Double data values that overflow to infinity [patch] #360
Changes from all commits
d5df749644a93fFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check warning on line 118 in Schema.Test/GeneratedDataEditorTests.cs
Use 'Assert.DoesNotContain' instead of 'Assert.IsFalse'
Check warning on line 126 in Schema.Test/GeneratedDataEditorTests.cs
Use 'Assert.Contains' instead of 'StringAssert.Contains'
Check warning on line 190 in Schema.Test/GeneratedDataEditorTests.cs
Use 'Assert.AreSequenceEqual' instead of 'CollectionAssert.AreEqual'
Check warning on line 206 in Schema.Test/GeneratedDataEditorTests.cs
Use 'Assert.IsNotEmpty' instead of 'Assert.AreNotEqual'
Check warning on line 209 in Schema.Test/GeneratedDataEditorTests.cs
Use 'Assert.AreSequenceEqual' instead of 'CollectionAssert.AreEqual'
Check warning on line 341 in Schema.Test/GeneratedDataEditorTests.cs
Use 'Assert.Contains' instead of 'StringAssert.Contains'
Check warning on line 351 in Schema.Test/GeneratedDataEditorTests.cs
Use 'Assert.AreSequenceEqual' instead of 'CollectionAssert.AreEqual'
Check warning on line 68 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 78 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 84 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 91 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 98 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 101 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.Contains' instead of 'Assert.IsTrue'
Check warning on line 102 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.Contains' instead of 'Assert.IsTrue'
Check warning on line 108 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 116 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 117 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 124 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 125 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 159 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 165 in Schema.Test/SchemaDataValidatorTypeTests.cs
Use 'Assert.IsEmpty' instead of 'Assert.HasCount'
Check warning on line 45 in Schema/Runtime/SchemaDataValues.cs
Loops should be simplified using the "Where" LINQ method
Check warning on line 209 in Schema/Runtime/SchemaDataValues.cs
Loops should be simplified using the "Where" LINQ method
Uh oh!
There was an error while loading. Please reload this page.