Warn on invalid responsive resource ranges - #11
Merged
Conversation
nicodes
force-pushed
the
issue-151-responsive-validation
branch
from
September 13, 2026 05:04
4b02736 to
c6e3da0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Self-verification evidence (Team No Review)
Issue: https://github.com/aviorstudio/fieldsofrevik/issues/151 — behavior layer stacked on #10. No review requested.
aviorstudio/gd-responsive,issue-151-responsive-validation, exact headc6e3da096caf5af21767e72f635cb598d473e5f9; baseline/known-good valid resource from73752cef4ca83ddd9691cf0f80e54a3e469a5b5d.min_content_width > max_content_width,min_scale > max_scale, andmobile_breakpoint >= tablet_breakpointproduced three field-specific warnings. All six artist edits emittedchangedand retained their exact values..tressaved and reopened with all values/warnings intact; layout warning propagation remained finite/stable; correcting only the conflicting minima/mobile breakpoint cleared resource and node warnings; recovered resource saved and reopened valid.GdResponsiveautoload.c3674be9a8b790bb91397b7e3f317ee20c4ccd64b0d2aa2f4d0c68ad1575b3bf; installed-tree SHA-256a94ef4aa969b33d6f7a8393df7985363af28f5940139ec314a19cc6782db0a82; web export passed. Personal playwright-cli 0.1.18 check at 960×720 loaded the packaged Godot export with zero console errors and visibly renderedGD Responsive Web Smoke PASS | device=0 | width=480../tests/test.sh; closed package build/verify; clean packaged editor enable/restart/validation/disable/restart; Godot 4.7.2 Web export;playwright-cli -s=gd-responsive open/reload/screenshotagainst local exact packaged export.@toolconfig, layout, inspector plugin, serialization and reopen all execute under the real 4.7.2 editor. The reproduced shutdown diagnostics are narrowly type-allowlisted only for scripted editor exit and are not attributed as a Godot defect.Correction — issue #151 stack replay
The native stack merge rebased this layer from
4b02736cf3bfdb88044760d6cff08fc9ff3ad743toc6e3da096caf5af21767e72f635cb598d473e5f9.git range-diffshowed all three commits as equivalent (=), and refreshed exact-head CI passed: 7 restored controls, 6 scripts, 21 editor assertions, 28-file package, Inspector validation, installed lifecycle, and web export. The head, run URL, package SHA, and screenshot URL above replace the superseded pre-rebase identities; installed-tree SHA remains unchanged.