Repository navigation
Describe generated photo and file uploads (plugin 0.8.4) - #122
Closed
raghubetina wants to merge 1 commit into
Closed
raghubetina wants to merge 1 commit into
raghubetina wants to merge 1 commit into
Conversation
The service's image-uploads Compiler release imports image and attachment Fields and generates Active Storage uploads on Cloudinary. The Plan reference still said those Fields are skipped, so an agent would promise a photo-less app. List both types as imported, say what they generate and what stays a gap, and keep the CLOUDINARY_URL instruction 0.8.3 added: setup works without it, and the first upload names it in a KeyError. The damage photo eval now expects a child Entity with one image Field instead of skipped gaps. Packaged bytes changed, so this targets plugin 0.8.4; it should publish only after that service release is deployed.
raghubetina
force-pushed
the
image-uploads
branch
from
October 4, 2026 22:47
30b1b02 to
3d3b73d
Compare
raghubetina
changed the title
Contributor
Author
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
1 participant
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.
Targets plugin 0.8.4. Rebased onto
mainafter 0.8.3 (#123/#124) shipped. Per the owner's 2026-10-04 decision, merge and publish this only after the First Draft service deploys the Compiler releasefoundation-plan-rails/compiler-application-2026-10-04-image-uploads(firstdraft/firstdraft branchimage-uploads). This PR publishes nothing.That release imports
imageandattachmentFields and generates Active Storage uploads stored on Cloudinary. The Plan reference still says these Fields are skipped, so an agent would promise a photo-less app.references/foundation-plan-023.md: addsattachmentandimageto the imported Field types and replaces the "skipped" sentences with what they generate and what stays a gap (public URLs, no type/size limits, one file per Field, no protected delivery, signup stays a partial gap for a required upload on the Account Entity). It keeps 0.8.3'sCLOUDINARY_URLinstruction and adds that setup works without it while the first upload raises aKeyErrornaming it.evals/create-full-stack-app/cases.json: the damage-photo expectation now wants a child Entity with one image Field instead of service-support gaps.plugin_source.tarball_sha256.Checked locally:
npm ci --ignore-scripts && npm audit(0 vulnerabilities),sh script/check --cli-root <pinned CLI 2f4bc93>(85 pass),node script/check-cli-contract.mjs <pinned CLI>, andnode script/check-plugin-release-order.mjs --prospective.Docs: updated skills/create-full-stack-app/references/foundation-plan-023.md and CHANGELOG.md