Jev diagnostic warning kind

Separate style warnings from behavior concerns

Supply the complete diagnostic list and the meaning of its entries. Check whether every warning is style-related or at least one concerns behavior.

Are all the supplied warnings about style or unused code?Live API
Try an example

Every warning concerns a formatting convention.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The API-collected roundup links the cited project. Its pinned source defines the decision adapted here. These synthetic inputs and explicit missing-context outcomes are original to this demonstration. The window returns a label; it does not run the linked application, execute its downstream actions or verify its performance claims.

First choose Need warnings for a missing, conflicting, empty or incomplete list, unresolved roles or a category outside this rule.

Decision rules and labels
Style onlyOther warning presentNeed warnings
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

One behavior warning changes the label for the whole list.

The formatting preset concerns indentation and whitespace. The unused-declaration preset also belongs to Style only under this page’s stated rule. That label describes a grouping, not a recommendation to ignore the warnings.

An unhandled save failure alongside a whitespace warning makes the mixed list Other warning present. An unexplained W42 code cannot establish either category when the supplied catalog gives conflicting meanings.

The source contains a separate question about whether new warnings concern only style or unused code. These synthetic lists adapt that question to three visible outcomes. The window does not run a linter, rank severity, establish that code is safe or suppress any warning.

The API-collected roundup links the cited project. Its pinned source defines the decision adapted here. These synthetic inputs and explicit missing-context outcomes are original to this demonstration. The window returns a label; it does not run the linked application, execute its downstream actions or verify its performance claims.

Illustration of checking a code change and reviewing a flagged line
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for diagnostic warning types.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Supply the complete diagnostic list and the meaning of its entries.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Style only, Other warning present, Need warnings. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Need warnings before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Formatting conventionsStyle only98.0%
Unused declarationsStyle only99.0%
Possible null dereferenceOther warning present98.0%
Formatting and behaviorOther warning present99.0%
Unresolved diagnostic meaningNeed warnings70.0%
Warnings absentNeed warnings100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Replay the saved synthetic requests to inspect each recorded decision

Replay the saved synthetic requests to inspect each recorded decision. Authored expectations and model disagreements remain available; these examples are not a production accuracy benchmark.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Grouping supplied diagnostic messages
  • Separating mixed behavior and style lists
  • Identifying unresolved warning codes

Outside this demonstration

  • Deciding which warnings are safe to ignore
  • Running static analysis
  • Assigning severity from an unfamiliar code alone
Example FAQ

Questions about diagnostic warning kind.

Input scope and downstream handling determine what this judgment means.

Why is unused code grouped with style?

The pinned source asks about style or unused code together. This page uses that same explicit group; it does not claim unused code is harmless in every system.

Does Other warning present rank the problem’s severity?

No. It says at least one supplied warning concerns behavior or correctness. Severity and the response to it need their own evidence and policy.

Is the leading probability an accuracy measurement?

No. It is one value in the returned distribution over this request’s choices. The six synthetic fixtures have authored expectations; they do not measure production accuracy.

What happens on an API failure?

The window displays an error without a fresh judgment. An incomplete-input outcome describes the supplied evidence and is not used as a fallback for provider failure.

Try your own diagnostic warning kind input

Edit the input above, or open the Playground to explore another decision.