feat: add Figma-native export functionality#4
Merged
Conversation
…ons and update plugin version to `0.3.0`
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.
FigGit v0.3.0 – Figma-Native Export Bundle
Unified Export Bundles
ExportBundleto normalize all export outputs, so UI, diffing, and commits consume a single structure regardless of format (buildExportBundle.ts,types/export.ts, messaging/context/plugin updates).Figma-Native Export Pipeline
buildFigmaNativeExportwith deterministic metadata, per-collection splitting, slugged filenames, alias resolution, andvalueNormalizationutilities.path.ts,slugify.ts,VariableModeValuerelocation) and comprehensive tests (figmaNativeExport.test.ts).GitHub Commit Improvements
commitFilesworkflow batches updates, reuses embeddedcontentHashdetection, and skips files already matching remote content.UI/UX Enhancements
ExportOptionsDisclosureso users choose DTCG vs Figma-native and single vs per-collection outputs.StatusSummary,JsonViewer, andDiffViewersurface per-document metadata, copy actions, and multi-file diffs with remote error handling.Docs & Packaging
READMEnow explains both schemas with example Figma-native JSON and revised distribution instructions.PLUGIN_VERSIONconstant set to0.3.0.