mirror of
https://github.com/jason5ng32/MyIP.git
synced 2026-11-04 08:55:47 +00:00
jason5ng32andClaude Fable 5.1
d5715104d5
Review findings on the ASN Profile work, mostly one class of bug: a failed upstream read as "no data", which the 7-day edge cache would then pin. - AS Rank: a 200 carrying GraphQL errors is a failure, not an unknown AS. - Radar: an answer built from partly failed segments is still shown but flagged `incomplete` and kept out of the cache, on the aggregate and on the standalone asn view. A 404 is Radar's "no such AS" and counts as empty, as does a segment that simply has no figures. - Reputation: a malformed or non-200 answer is an error. - Prefixes: a payload without `prefix_origins` is an error; [] stays valid. - Radar is `empty` when only local CAIDA counts are present. - requireValidASN enforces AS1–AS4294967295 and canonicalizes; the range rule lives once in common/asn-input.js, shared with the frontend. - The PeeringDB listing lookup goes through fetchUpstream. - New functions follow the const-arrow convention; test stubs compare parsed hostnames instead of URL substrings. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
4 lines
200 B
JavaScript
4 lines
200 B
JavaScript
// Thin re-export of common/asn-input.js (shared with the ASN guards), so
|
|
// front-end code keeps importing `@/utils/asn-input.js`.
|
|
export { MAX_ASN, parseAsnInput } from '../../common/asn-input.js';
|