네트워크가 찾아낸 것
아래 각 줄은 의견이 아니라 측정입니다. 모두 공개된 샘플로 연결되며, 그 샘플의 contract는 네트워크를 끈 고정 컨테이너에서 실행되므로 직접 다시 돌려 보고 반박할 수 있습니다.
운영체제와 런타임은 연결된 샘플에 실제 기록된 환경을 기준으로 합니다. 해당 값이 없는 항목은 필터 선택 시 제외됩니다.
597개 발견, 8개 생태계.
- cargo
- composer
- gem
- golang
- hex
- npm
- pub
- pypi
샘플이 말하고, 계약이 측정한 것
발행된 샘플이 측정한 결과 중 376–400번째입니다(전체 568개).
-
npm샘플 컨트랙트node · linux/x64core-js@3.49.0
믿는 것A naive expectation is that `Iterator.range` coerces `NaN` arguments to usable numbers, so `Iterator.range(NaN, 10)` would still return an iterable.
측정한 것Calling `Iterator.range` with `NaN` as `start` throws `RangeError` in the patched `core-js` behavior.
-
npm샘플 컨트랙트node · linux/x64commander@15.0.0
믿는 것An option configured with an optional value accepts negative numbers like -1 as its argument regardless of what other short option flags are registered on the command.
측정한 것Passing -1 after an optional-argument option evaluates that option to boolean true and parses -1 as a distinct flag if any single-digit short option is defined on the command hierarchy, because Commander disables negative number heuristics whenever a digit flag exists.
-
npm샘플 컨트랙트node · linux/x64commander@13.1.0
믿는 것Parsing multiple command invocations concurrently with parseAsync on a shared Command instance keeps options isolated within each execution promise.
측정한 것Calling parseAsync on a shared Command instance while an earlier parseAsync execution is suspended at an await overwrites the option store, causing the earlier execution to resume with option values from the later invocation.
-
npm샘플 컨트랙트node · linux/x64commander@15.0.0
믿는 것An option configured with an optional value and a custom argParser coerces a fallback value through argParser when the flag is invoked without an argument on the command line.
측정한 것Option.preset() supplies a fallback value passed to argParser when an optional-value flag is invoked without arguments, preventing Commander from storing boolean true and bypassing custom parser coercion.
-
npm샘플 컨트랙트node · linux/x64bun@1.3.14
믿는 것Pinning bun in package.json should let Node import it as a normal dependency module.
측정한 것bun@1.3.14 has no Node import surface in lockfile metadata, because neither `main` nor `exports` is present even though the package is installed as a dependency.
-
npm샘플 컨트랙트node · linux/x64bun@1.3.14
믿는 것Bun binary APIs receive a typed array's entire backing ArrayBuffer, so passing a subarray with a non-zero offset hashes, compresses, or writes bytes outside the view.
측정한 것Bun.hash produces the same result for a non-zero-offset Uint8Array view and an independent array containing only the view bytes, and a different result for the full backing array
-
npm샘플 컨트랙트node · linux/x64@babel/preset-env@7.26.9
믿는 것Targeting modern environments like Node 22 or setting targets.esmodules to true causes @babel/preset-env to preserve ES module import and export syntax by default without transforming them to CommonJS.
측정한 것Even when targeting modern environments that natively support ES modules such as Node 22 or esmodules: true, @babel/preset-env defaults modules to 'auto' and transforms import and export statements into CommonJS require and exports unless the caller declares supportsStaticESM or modules is explicitly set to false.
-
npm샘플 컨트랙트node · linux/x64@babel/preset-env@8.0.2
믿는 것Targeting modern JavaScript runtimes with @babel/preset-env and default modules: 'auto' preserves native export * as ns syntax because the targeted environments natively support ECMAScript namespace re-exports.
측정한 것When modules is unset or 'auto', @babel/preset-env unconditionally injects transform-export-namespace-from and desugars export * as ns statements even when targeting modern runtimes like Chrome 120 or Node 22, unless modules is explicitly false or the caller declares supportsExportNamespaceFrom.
-
npm샘플 컨트랙트node · linux/x64@babel/core@8.0.1
믿는 것Equivalent inline plugin option objects are reused across transformSync calls, and createConfigItem remains a synchronous convenience API in Babel 8.
측정한 것A ConfigItem created once with createConfigItemSync reuses its plugin descriptor so five transformSync calls execute the factory exactly once
-
npm샘플 컨트랙트node · linux/x64@babel/core@8.0.1
믿는 것Calling babel.transformAsync allows plugin visitor methods to be async functions whose returned Promises are awaited before AST traversal completes and transformed output code is generated.
측정한 것babel.transformAsync completes AST traversal synchronously and generates untransformed output code when a plugin visitor returns a Promise, leaving the Promise un-awaited.
-
npm샘플 컨트랙트node · linux/x64@babel/core@8.0.1
믿는 것transformFromAstSync modifies the provided AST object in place during traversal and populates result.ast with the transformed tree.
측정한 것transformFromAstSync preserves the input AST node unmodified and sets result.ast to null unless cloneInputAst is set to false and ast is set to true.
-
npm샘플 컨트랙트node · linux/x64@babel/core@8.0.1
믿는 것babel.transformSync automatically discovers and loads .babelrc configuration files from the current working directory when transforming code strings.
측정한 것babel.transformSync and babel.loadPartialConfigSync ignore .babelrc configuration files when filename is omitted, defaulting options.babelrc to false
-
npm샘플 컨트랙트node · linux/x64@babel/core@8.0.1
믿는 것Setting configFile: false disables all filesystem configuration loading, while subpackage .babelrc.json configurations are discovered and applied automatically.
측정한 것Setting configFile: false disables only project-wide babel.config.json while leaving file-relative .babelrc.json active, and subpackage .babelrc.json files are ignored under default babelrcRoots: true
-
hex샘플 컨트랙트elixir · linux/x64nimble_pool@1.1.0
믿는 것NimblePool.handle_info/2 follows the same return convention as GenServer.handle_info/2, accepting (message, state) and returning {:noreply, state}, because NimblePool is built on GenServer.
측정한 것Returning {:noreply, worker_state} from handle_info/2 crashes the pool process with CaseClauseError, because NimblePool routes stray messages to each idle worker's handle_info/2, then pattern-matches the result against {:ok, _}, killing the pool and making all subsequent checkouts exit with :noproc.
-
golang샘플 컨트랙트go · linux/x64net/http@go1.26.5
믿는 것Headers set on http.ResponseWriter after calling WriteHeader are included in the HTTP response.
측정한 것Headers set on http.ResponseWriter after calling WriteHeader are omitted from the client response.
-
golang샘플 컨트랙트go · linux/x64net/http@v1.26.5
믿는 것Setting the Host header via http.Request.Header.Set("Host", ...) overrides the Host header sent on the wire by http.Client.
측정한 것req.Header.Set("Host", ...) does not override the wire Host header sent by http.Client
-
golang샘플 컨트랙트go 1.26 · linux/x64gorm.io/gorm@v1.31.2
믿는 것Calling Scopes(Tenant(id)) before Where(...).Or(...) keeps the tenant predicate in force for both OR branches because the scope appears first in the chain.
측정한 것assert Scopes(Tenant(7)).Where("active = ?", true).Or("role = ?", "admin") generates WHERE active = ? OR role = ? AND tenant_id = ?, so SQL precedence allows active rows from other tenants
-
golang샘플 컨트랙트go 1.26 · linux/x64google.golang.org/grpc@v1.83.0
믿는 것A unary client interceptor can call metadata.NewOutgoingContext to add its own field without affecting outgoing metadata the caller already attached.
측정한 것A grpc.NewClient call reaches a manually registered unary service through bufconn, a context dialer, and insecure transport credentials without opening a TCP listener.
-
golang샘플 컨트랙트go 1.26 · linux/x64github.com/spf13/viper@v1.21.0
믿는 것MergeConfigMap treats its argument as immutable input and copies it, so changing or reusing the caller's map after the call cannot alter Viper's configuration.
측정한 것assert MergeConfigMap lowercases both top-level and nested keys in the caller-supplied maps themselves
-
golang샘플 컨트랙트go · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
믿는 것providing an invalid key type (such as a byte slice instead of an RSA public key) to jwt.Parse during RSA verification returns jwt.ErrTokenUnverifiable or jwt.ErrInvalidKeyType rather than jwt.ErrTokenSignatureInvalid
측정한 것assert jwt.Parse returns jwt.ErrTokenSignatureInvalid when a key of invalid type is provided for RSA verification, rather than ErrTokenUnverifiable or ErrInvalidKeyType directly
-
golang샘플 컨트랙트go · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
믿는 것Defining a Valid() error method on a custom claims struct in github.com/golang-jwt/jwt/v5 triggers custom validation during parsing, and missing expiration claims cause parsing to fail by default.
측정한 것Defining a Valid() error method on a custom claims struct has no effect in v5 because custom validation requires implementing the jwt.ClaimsValidator interface via a Validate() error method.
-
golang샘플 컨트랙트go · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
믿는 것A single-element jwt.ClaimStrings slice serializes to a JSON string value by default.
측정한 것Serializing a single-element jwt.ClaimStrings audience produces a JSON array by default because jwt.MarshalSingleStringAsArray is true.
-
golang샘플 컨트랙트go · linux/x64github.com/golang-jwt/jwt/v5@v5.2.2
믿는 것ParseUnverified returns a slice containing all split string segments when parsing a malformed token string with extra dot delimiters.
측정한 것ParseUnverified returns a nil parts slice rather than a populated slice of all split segments when given a token with extra dot delimiters.
-
golang샘플 컨트랙트go · linux/x64github.com/golang-jwt/jwt/v5@v5.3.1
믿는 것Defining a Valid() error method on a custom claims struct validates claims during jwt.ParseWithClaims.
측정한 것jwt.ParseWithClaims silently ignores a custom claims Valid() error method, passing validation unless the struct implements ClaimsValidator with Validate() error.
-
golang샘플 컨트랙트go · linux/x64github.com/go-chi/chi/v5@v5.2.1
믿는 것middleware.AllowContentType rejects POST requests lacking a Content-Type header and ignores Content-Type headers on GET requests.
측정한 것middleware.AllowContentType allows a body-less POST request with an empty Content-Type header through to the handler with HTTP 200 rather than rejecting it based on the HTTP method
여기 있는 줄을 확인하는 방법
샘플을 열고 contract를 읽고 실행하십시오. contract는 그 샘플 자신의 테스트입니다. 네트워크를 끈 고정 컨테이너에서 실행되고, 그 실행의 서명된 영수증이 네트워크에 저장됩니다. 여기 있는 어떤 것도 라이브러리에 대한 우리의 해석에 기대지 않습니다. 라이브러리가 실제로 한 일에만 기댑니다.
게시된 샘플 중 일부는 이 페이지에 없습니다. 계약은 통과했고 샘플도 살아 있지만, 그 계약에 문장으로 읽힐 줄이 없기 때문입니다. expect(x).toBe(1) 같은 단언은 그것이 검사하는 믿음 옆에 놓아도 독자에게 아무것도 말해주지 않습니다. 읽을 수 없는 근거를 싣기보다는 뺀다는 쪽을 택했습니다.