Change:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --Hello! Could you please allow for the output.ReverseAttributes to be defined as a user preference setting? This was implemented to and was implemented in the current emmet repo Why is this important? With Bootstrap, all of the generated code samples implement class attributes at the beginning of a tag. For example, a generated (As a note, this is how I've generally seen and used bootstrap classes implemented inside a tag), might have a section that looks like this: to add a new anchor with the same syntax, I would want to use the follow emmet syntax: However, the preview generated, and the implementation do not give me the style that I prefer: ! Now, I could implement a snippet for this specific anchor override, but now if I want to use this style across the codebase with all of my tags that utilize bootstrap, I now have to create a file that grows exponentially to cover every use-case. Since solves this behavior, I figured I could do add this override in my code workspace settings, such as But this did not work. also does not have a supported object for preferences based on . I think this might also open a bigger question of "How can VSCode support any arbitrary snippet preference? (There are many from where this specific attribute was implemented) There doesn't seem to be a method to implement this behavior via the regular so if I want this behavior today, it seems I would need to fork emmet and vscode, and implement my own custom implementation to enable this feature toggle.
thanks for the write-up. I wasn't aware of when output.reverseAttributes would come in handy. What I do know though, is that VS Code is currently using an older version of Emmet. Once it moves on to the newer version (the one you see at emmetio/emmet), it should be much simpler to get that preference implemented. I'll keep this issue open in the meantime.
Sounds great! Thanks for the quick response, looking forward to the newer version of Emmet being implemented!
Created a PR fixing this

Discussion:
"type": "number", "default": 0.3, "description": "%emmetPreferencesCssFuzzySearchMinScore%" <ins> }, "output.reverseAttributes": { "type": "boolean", "default": false, "description": "%emmetPreferencesOutputReverseAttributes%" </ins> } } },

"emmetPreferencesCssOProperties": "Comma separated CSS properties that get the 'o' vendor prefix when used in Emmet abbreviation that starts with `-`. Set to empty string to always avoid the 'o' prefix.", "emmetPreferencesCssMsProperties": "Comma separated CSS properties that get the 'ms' vendor prefix when used in Emmet abbreviation that starts with `-`. Set to empty string to always avoid the 'ms' prefix.", "emmetPreferencesCssFuzzySearchMinScore": "The minimum score (from 0 to 1) that fuzzy-matched abbreviation should achieve. Lower values may produce many false-positive matches, higher values may reduce possible matches.", <del> "emmetOptimizeStylesheetParsing": "When set to `false`, the whole file is parsed to determine if current position is valid for expanding Emmet abbreviations. When set to `true`, only the content around the current position in css/scss/less files is parsed." </del> <ins> "emmetOptimizeStylesheetParsing": "When set to `false`, the whole file is parsed to determine if current position is valid for expanding Emmet abbreviations. When set to `true`, only the content around the current position in css/scss/less files is parsed.", "emmetPreferencesOutputReverseAttributes": "If `true`, reverses attribute merging directions when resolving snippets." </ins> }