a

This contains the basic code generates the text, inserte it, Maintain a snippet state, as well as dragonfly actions to wrap things up

…of function

I hope this solves the deprecation errors that Appear in the checks

I accidentally put this comment in the wrong place with my previous commit

…ork to be done

…pted values fails

this was actually causing problem when dealing with lists but the solution should be more general

…iple times if module is reloaded

…orts

…ion context

also contains a cleanupFrom debugging printing statements

With this change The decorator can be used in two ways Both standalone and with parameters

motivation: Snippet is supposed to be able to remap extras the appropriate lambda parameters and those final parameter names along with the extra values are stored in the snippet state under the key "extra_data". However for the control grammar to be able to work, we also need to make sure that it knows the renaming that just happened as it will generate all of the variance using the extras from the rules themselves!

they should be working, though I do have to say That having remapping of extras Both in the snippet auction in a manner similar to that of dragonfly Function And in the decorator to specify the spoken form of an extra might be a cause of confusion

up until now, to register the call back the function register_post_recognition_callback was used in a way that allowed reregistering the same callback if the grammar reloads! we now subclass the dragonfly recognition observer and add codein order to allow one instance to be to run the call back!

… for shallow choices and integers

The current implementation suite is from doing a lookup in the data collected from the decorator mark_snippet_grammar based on the type of the rule inserted to obtaining the data directly from the callback rule Even if it  is CCR Or self modifying! Under these circumstances, checking if their last rule belong to grammars_with_snippets becomes redundant and unreliable and has been commended out

…SublimeSnippetAdditionalRule

In general it was expected that self modifying rules Might need a toml Configuration file in order to save their state. However,for rules like the snippet control rule introduced by dictation-toolbox#775 is not the case and being forced to Specify a configuration file from which they will write and read Whenever it needs to refresh is simply a burden and a waste of additional time. With this solution Such grammars can use None/"" in order to specify that they do not want a configuration file

Short commit because previous changes were lost

Now,snippet_state should be modified in place, without messing up initial_snippet_state

…he controlled grammar

…somewhat similar manner to Key

… py2