Alex Garel

@alexfauquette can you tell us, how it's setup in hungergames ?

@eric-nguyen-cs I 100% agree on sharing same code. But the dependency should be the other way around. I want the parser to be a reusable library (to unable other usages),...

BTW you can put models in the parser of course, this is a good idea.

@eric-nguyen-cs I propose we discuss this on next meeting. I would like to keep it simple. The parser can be a simple library with good entry points and the backend...

After some though, I think your initial proposal is the correct one @eric-nguyen-cs with one difference: put models and neo4j backend in parser library (neo4j stuff being in it's own...

As discuss, my opinion is: Enclosing, by default, http request in transactions is a fool proof mechanism and we want to keep it (business inconsistencies in a database is a...

@AnshSinghSonkhia please do not copy paste response from a chatbot… we can use one ourselves if we need.

@BryanH01 there has been a misunderstanding here (sorry for that). I didn't want you to add the checks at parsing time, nor statically. What should be done is a checks.py...

@teolemon this PR is stalled and it does not do the checks the way we want them (we a live API), we keep it just for the neo4j request that...

> BTW what is this taxonomy-editor-frontend/build directory you added ? Sorry I misread this, it was removed, but it makes your tests fail… you should not remove the build/.empty file,...