Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emmet: Missing possibility to encode/decode an image #27978

Closed
jens1o opened this issue Jun 3, 2017 · 11 comments
Closed

Emmet: Missing possibility to encode/decode an image #27978

jens1o opened this issue Jun 3, 2017 · 11 comments
Assignees
Labels
emmet Emmet related issues feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities

Comments

@jens1o
Copy link
Contributor

jens1o commented Jun 3, 2017

  • VSCode Version: Code - Insiders 1.13.0-insider (f977399, 2017-06-02T10:54:04.063Z)
  • OS Version: Windows_NT ia32 10.0.15063
  • Extensions:
Extension Author Version
vscode-reveal evilz 0.0.9
php-intellisense felixfbecker 1.3.0
auto-close-tag formulahendry 0.4.2
php-docblocker neilbrayfield 1.2.0
vscode-icons robertohuertasm 7.8.1
Material-theme zhuangtongfa 2.8.4

Steps to Reproduce:

  1. Try to encode an image
  2. See that there is no command to do so
  3. Lookup the manual and recognize this exists: https://docs.emmet.io/actions/base64/
@vscodebot vscodebot bot added the insiders label Jun 3, 2017
@ramya-rao-a
Copy link
Contributor

@mrmlnc did work on this one a while ago
See #9002

But that didn't make it and one of the main reasons was that the dependent version of the emmet module go too big.

@mrmlnc You want to give this another try in the new emmet extension?

@ramya-rao-a ramya-rao-a added feature-request Request for new features or functionality emmet Emmet related issues labels Jun 5, 2017
@ramya-rao-a ramya-rao-a added this to the Backlog milestone Jun 5, 2017
@ramya-rao-a ramya-rao-a added the help wanted Issues identified as good community contribution opportunities label Aug 2, 2017
@chrmarti chrmarti removed the insiders label Sep 27, 2017
@ramya-rao-a ramya-rao-a added the *out-of-scope Posted issue is not in scope of VS Code label Feb 5, 2018
@vscodebot
Copy link

vscodebot bot commented Feb 5, 2018

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that have been on the backlog for a long time but have not gained traction: We look at the number of votes the issue has received and the number of duplicate issues filed. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Feb 5, 2018
@jens1o
Copy link
Contributor Author

jens1o commented Feb 5, 2018

@ramya-rao-a Can you elaborate on why this doesn't fit anymore?

@ramya-rao-a
Copy link
Contributor

@jens1o As explained in #27978 (comment), there hasn't been any traction on this feature request. Neither in terms of user interest or in terms of PRs from the community.

We can't just use the Emmet library that does support this feature because we have moved on to using the newer Emmet modules.

@sergeche Correct me if I am wrong, but I believe there are no Emmet modules currently that can help with this feature. Do you have plans of adding any?

@jens1o
Copy link
Contributor Author

jens1o commented Feb 5, 2018

That's a pity. :/

@sergeche
Copy link

sergeche commented Feb 6, 2018

There is such action in Atom: https://github.com/emmetio/atom-plugin/blob/master/lib/actions/convert-data-url.js
Since this action requires user interaction and file access, it should have editor-specific implementation mostly.

@ramya-rao-a
Copy link
Contributor

Thanks for the pointer @sergeche

Re-opening this, if anyone is interested in contributing.

@ramya-rao-a ramya-rao-a reopened this Feb 6, 2018
@ramya-rao-a ramya-rao-a removed the *out-of-scope Posted issue is not in scope of VS Code label Feb 6, 2018
@jens1o
Copy link
Contributor Author

jens1o commented Feb 6, 2018

Yeeey.. Thank you!

Unfortunately, I lack of time to get used to the refactored codebase :/

@vscodebot
Copy link

vscodebot bot commented Jan 16, 2020

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodebot
Copy link

vscodebot bot commented Mar 6, 2020

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

@vscodebot
Copy link

vscodebot bot commented Mar 16, 2020

🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Mar 16, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Apr 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
emmet Emmet related issues feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities
Projects
None yet
Development

No branches or pull requests

7 participants