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 expansion seems to break when enabling SublimeBabel #25

Closed
jtokoph opened this Issue Sep 14, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@jtokoph

jtokoph commented Sep 14, 2017

Example code:

import React from 'react';

export default class Test extends React.Component {
  render() {
    return (
      .foo
    );
  }
}

If I expand the .foo with emmet, it works fine and I end up with:

import React from 'react';

export default class Test extends React.Component {
  render() {
    return (
      <div className="foo"></div>
    );
  }
}

If I then try to expand another time inside like so:

import React from 'react';

export default class Test extends React.Component {
  render() {
    return (
      <div className="foo">
        .bar
      </div>
    );
  }
}

Emmet won't expand the .bar

If I disable SublimeBabel, the .bar expansion works as expected

@jtokoph

This comment has been minimized.

Show comment
Hide comment
@jtokoph

jtokoph Sep 14, 2017

I forgot to include some configuration information:

I have the following emmet related configuration options set:

{
  "emmet.syntaxProfiles": {
    "javascript": "jsx"
  },
  "emmet.showExpandedAbbreviation": "never",
  "emmet.showAbbreviationSuggestions": false
}

It seems like removing the last two configuration options I can at least get the suggested expansions to work, but using a bound hot key or manually invoking the expand abbreviation action from the command pallet still won't work.

jtokoph commented Sep 14, 2017

I forgot to include some configuration information:

I have the following emmet related configuration options set:

{
  "emmet.syntaxProfiles": {
    "javascript": "jsx"
  },
  "emmet.showExpandedAbbreviation": "never",
  "emmet.showAbbreviationSuggestions": false
}

It seems like removing the last two configuration options I can at least get the suggested expansions to work, but using a bound hot key or manually invoking the expand abbreviation action from the command pallet still won't work.

@joshpeng

This comment has been minimized.

Show comment
Hide comment
@joshpeng

joshpeng Sep 14, 2017

Owner

Hi @jtokoph Try removing all emmet config settings. It seems to work on my end with nothing configured for it.

Owner

joshpeng commented Sep 14, 2017

Hi @jtokoph Try removing all emmet config settings. It seems to work on my end with nothing configured for it.

@joshpeng

This comment has been minimized.

Show comment
Hide comment
@joshpeng

joshpeng Sep 16, 2017

Owner

Please reopen if you still have issues.

Owner

joshpeng commented Sep 16, 2017

Please reopen if you still have issues.

@joshpeng joshpeng closed this Sep 16, 2017

@EQuimper

This comment has been minimized.

Show comment
Hide comment
@EQuimper

EQuimper Sep 18, 2017

Hey @joshpeng I just get the same error like @jtokoph . I try removing all the emmets config but that still break. My first component can get trigger by emmet tab. But the second one never. But if I disable this package all work like suppose. :s Any idea what I can do for making work ?

EQuimper commented Sep 18, 2017

Hey @joshpeng I just get the same error like @jtokoph . I try removing all the emmets config but that still break. My first component can get trigger by emmet tab. But the second one never. But if I disable this package all work like suppose. :s Any idea what I can do for making work ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment