Fixed #3: Added sheerka.resolve_rule()

Fixed #5: Refactored SheerkaComparisonManager
Fixed #6: Sya parser no longer works after restart

docs/source/README.txt

@@ -4,4 +4,5 @@ install the following extensions:
 * LiveServer (from Ritwick Dey)
 * reStructuredText (from Lextudio Inc)
 doc page for reStructuredText : https://docs.restructuredtext.net/
-shortcuts : https://docs.restructuredtext.net/articles/shortcuts.html
+shortcuts : https://docs.restructuredtext.net/articles/shortcuts.html
+doc de sphinx : https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html

docs/source/blog/blog.rst

@@ -1,11 +1,3 @@
-.. toctree::
-    :maxdepth: 1
-
-    concepts
-    rules
-    parsers
-    persistence
-
 
 2019-10-30
 **********

docs/source/conf.py

@@ -18,7 +18,7 @@
 # -- Project information -----------------------------------------------------
 
 project = 'Sheerka'
-copyright = '2020, Kodjo Sossouvi'
+copyright = '2020-2001, Kodjo Sossouvi'
 author = 'Kodjo Sossouvi'
 
 # The full version, including alpha/beta/rc tags
@@ -52,4 +52,4 @@ html_theme = 'alabaster'
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = ['_static']
+html_static_path = ['_static']

docs/source/index.rst

@@ -1,6 +1,10 @@
 Sheerka's documentation!
 ===================================
 
+.. WARNING::
+
+   Under construction for one year !
+
 Hi, welcome the the documentation page of Sheerka. 
 There will be two types of documentation
    
@@ -15,11 +19,14 @@ There will be two types of documentation
 
    blog/blog
 
+
 .. toctree::
    :maxdepth: 1
    :caption: Technical Design:
 
    tech/tech
+   tech/debugger
+
 
 
 Indices and tables

docs/source/tech/debugger.rst

@@ -0,0 +1,19 @@
+Debugger
+========
+
+Abstract
+--------
+The purpose of the debugger is to ease to understand why Sheerka does not behave like it should.
+(yes, this could happen). I have have just started so, they are a lot of 
+functionalities that we usually found in a debugger that are not yet implemented
+
+I guess that the first thing to know is that I want to design a 'smart' debugger,
+which can be configured in a 'declarative' way. It means that, rather that telling
+it what to do, I would prefer tell it what is expected.
+
+As of now (2021-01-11), I am far from it, so let's explain how to use the debugger,
+in an 'imperative' way.
+
+First, you need to enable the debugger. As it consumes resource, it is deactivated by default ::
+    
+    set_debug()