All snippets miss a scope

[deathaxe]

All your snippets miss the <scope>text.html.markdown</scope> keys, which causes them to be suggested in any syntax.

Example

Current h1.sublime-snippet

<snippet>
    <content><![CDATA[
# ${1:text here}
]]></content>

<tabTrigger>mdh1</tabTrigger>

    <description>Creates a heading 1(For .md files)</description>
</snippet>

Prefered h1.sublime-snippet

<snippet>
	<content><![CDATA[
# ${1:text here}
]]></content>
	<tabTrigger>mdh1</tabTrigger>
	<scope>text.html.markdown</scope>
	<description>Creates a heading 1</description>
</snippet>

[code-reaper08]

Hey ! @deathaxe

It seems like it already has the exact same scope for all snippets as you conveyed in the raised issue.
Please check it once.

It appears to me as in the attached screenshot .

[deathaxe]

This is what the files look like in the package installed via Package Control.

It appears you need to make a new release, only, then.

[code-reaper08]

@deathaxe hey that's a good point out ,donno why it's happening like that.

I have scopes defined in my repo, yet users get files without scope.

Interesting 😵

If a new release would solve the problem I would definitely do it ASAP.

In regarding that description part, I will change it too.

Thanks for pointing it out 😁👍👌

[deathaxe]

Maybe one further addition may be useful.

In order to prevent snippets from being triggered within fenced code blocks you might want to modify the scope to <scope>text.html.markdown - meta.code-fence - markup.raw</scope>

[code-reaper08]

Hey @deathaxe
Sorry for replying so late 😅

I'll do it ASAP with the scope part.
💯👍

Thanks for letting me know the issue.

[code-reaper08]

@deathaxe see this

feel free to open any issues

Thanks for making it better 😃✨❤