Version 11 broke syntax highlighting. about babel-sublime HOT 15 CLOSED

This is the deliberate result of changes to the consensus on scope naming. In the guidelines, storage.type is used for type names in C-style declarations like int foo;. Since then, storage.type has generally been used for non-type variable declaration keywords like const. After much discussion, the community decided to reserve storage.type for types and use keyword.declaration for other declaratory keywords.

If you prefer the old behavior, you can modify your color scheme to highlight keyword.declaration the same as storage.type.

from babel-sublime.

from babel-sublime.

Awesome, thanks!
Simple fix for my Monokai Phoenix.tmTheme and voila! Here is my previous beloved color scheme 🚀

What i was need:

<dict>
  <key>name</key>
  <string>keyword.declaration</string>
  <key>scope</key>
  <string>keyword.declaration</string>
  <key>settings</key>
  <dict>
    <key>foreground</key>
    <string>#66D9EF</string>
  </dict>
</dict>

PS:
more info for customization here:
https://www.sublimetext.com/docs/scope_naming.html#keyword
https://www.sublimetext.com/docs/scope_naming.html#storage

from babel-sublime.

Looks like a bug in arrow function return type argument handling in Flow. Can reproduce.

from babel-sublime.

Should be fixed in v11.0.1. Thanks for the report.

from babel-sublime.

v11.0.1 installed. Not working yet.

from babel-sublime.

Can you paste the errant code as text?

from babel-sublime.

const ItemLookupScreen = (props: any): React.Node => {
  const data = useContext(DataContext);
  const navigation = useNavigation();
  const {
    request,
    loading,
    error,
    result: apiResult,
  } = useApiAuth(data.apiConfig, 'Items');

  const { setParam, params, ...paginated } = usePaginated(Initial, apiResult);
  const [textFilter, setTextFilter] = useState('');

  useEffect(() => {
    setParam({ filtroTexto: textFilter });
  }, [setParam, textFilter]);

  const seleccionar = (item: ItemDTO) => {
    navigation.navigate('EditarItem', {
      item,
    });
  };

  useEffect(() => {
    request(params);
  }, [request, params]);

  return null;
}

from babel-sublime.

v11.0.2 is out with a couple more Flow fixes. Please let me know if this fixes it.

from babel-sublime.

Hello friends,

I'm running the latest version (v11.0.2) and the syntax highlight is still broken for me:

from babel-sublime.

Can you post the complete text of the file? Or a complete working example?

from babel-sublime.

@darve I can't reproduce. Since highlighting is messed up at the beginning of that excerpt, it probably means that the error occurs in other code before the excerpt. Without seeing more of the code, I can't troubleshoot it.

from babel-sublime.

@darve Is this still broken, or did it turn out to be something else?

from babel-sublime.

Hi @Thom1729
I just found that last 2 versions also changed the color of reserved words like const / let / function
Before

After

from babel-sublime.

It would appear it is working as intended then, because I have the same issue as @maullerz... I just assumed it was doing that because something was broken because it looks mighty strange!

from babel-sublime.