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 abbreviation with (...)*n doesn't work #27784

Closed
roblourens opened this issue May 31, 2017 · 11 comments
Closed

Emmet abbreviation with (...)*n doesn't work #27784

roblourens opened this issue May 31, 2017 · 11 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug emmet Emmet related issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Milestone

Comments

@roblourens
Copy link
Member

roblourens commented May 31, 2017

#27316

  • div*2 produces 2 divs
  • (div)*2 and (div>span)*2 expand -> the abbreviation is replaced with empty string

Works with old emmet

@ramya-rao-a ramya-rao-a added bug Issue identified by VS Code Team member as probable bug emmet Emmet related issues labels May 31, 2017
@ramya-rao-a ramya-rao-a added this to the June 2017 milestone May 31, 2017
@ramya-rao-a
Copy link
Contributor

@sergeche abbreviations like (...)*n are getting expanded to empty string when using https://github.com/emmetio/expand-abbreviation

For example: The below case

image

expands to just

<div>
    <dl></dl>
</div>
<footer>
    <p></p>
</footer>

Is this a known issue?

@ramya-rao-a ramya-rao-a added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Jun 2, 2017
@jens1o
Copy link
Contributor

jens1o commented Jun 3, 2017

No, it is not a known issue. The old emmet IS able to resolve it.

Edit: Unfortunately, I can't provide a gif because it would be more than 10MB. :/

@ramya-rao-a
Copy link
Contributor

@jens1o yes, it works in old emmet.

I meant to ask if it is a known issue in the new one or @sergeche would prefer me logging a new issue.

Thanks for looking into it though. Let us know if you find any other feature that previously worked but doesn't now with the new emmet

@jens1o
Copy link
Contributor

jens1o commented Jun 3, 2017

I do, don't mention it. 😉

@ramya-rao-a
Copy link
Contributor

Logged emmetio/atom-plugin#23 for upstream issue

@ramya-rao-a
Copy link
Contributor

@sergeche I have created a PR to fix this issue. emmetio/output-renderer#1

Can you please take a look.

Grouping seems to be one of the important cases in emmet abbreviations.

@jens1o
Copy link
Contributor

jens1o commented Jul 29, 2017

It has been merged, so this issue can be resolved, can't it?

@ramya-rao-a
Copy link
Contributor

Re-opening as nested groups are still not working as expected

Eg: (div>dl>(dt+dd)*2) eventually gets expanded to

    <div>
       <dl></dl>
   </div>
   <dt></dt>
   <dd></dd>
   <dt></dt>
   <dd></dd>

instead of

    <div>
       <dl>
          <dt></dt>
          <dd></dd>
          <dt></dt>
         <dd></dd>
       </dl>
   </div>

PR to upstream repo has been submitted emmetio/abbreviation#4

@jens1o
Copy link
Contributor

jens1o commented Aug 1, 2017

Then you might want to actually open it again? @ramya-rao-a

@ramya-rao-a
Copy link
Contributor

haha! thought I did.

@ramya-rao-a ramya-rao-a reopened this Aug 1, 2017
@ramya-rao-a
Copy link
Contributor

Upstream PR emmetio/abbreviation#4 is merged and the changes are pulled into VS Code as well.

@chrmarti chrmarti added the verified Verification succeeded label Aug 2, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug emmet Emmet related issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants