Not enough information about how to handle complex model relations about symlex HOT 7 CLOSED

Ah, and I would like to add: I am posting here because it looks very interesting what you did! I immediately liked the approach because I often have to shake my head about the unbelievable and unneccessary overhead of symfony - so some "clear mind" solution is absolutely welcome!

The issues I am posting are just some small, but very important things missing - please keep up this fantastic work, it is not meant to frustrate you. With these few issues resolved I can see this framework replace many bloated things in a few weeks with great success!

from symlex.

I could show you (maybe via chat). For example, you could use a form, get values by tag (instead of getting all values) and assign them to a model. Or you can access single values and assign them to model values manually. It totally depends on your code and your style. But the simple solution is to tag your form fields (should be documented, but more example would certainly be nice - maybe somebody can contribute them?).

from symlex.

PS: Don't expect a lot of magic and annotations that do things for you somehow.

from symlex.

hmm, I found three entries mentioning "tags" in the docs, however these do not explain anything about how to define relationships in the models or how to create master-detail views of multiple connected models.

I certainly at this point can not contribute to the docs, as I am just trying to understand how your framework works, but I hope I may be allowed to give a hint about the docs: it is a bit unclear about the boundaries between your code and the involved frameworks, where "symfony practices" can be applied and where doctrine docs are valid.

It would be great if the doc writer assumed, that the reader does not completely know all of symfony and all of doctrine, so it would be great to precisely show where knowledge from these other frameworks needs to be applied.

E.g. I can find no info in the docs for important things like "onetomany" or "manytomany" ("no matching documents", also reading the db layer docs I did not found anything) so it is a mystery how these kind of relations should be implemented with your framework.

from symlex.

Haha, yes, you have to code that. I think there are a few helper methods in the Entity DAO for the SQL. But at the end you have to write code like that:

class User {
  function getComments() {
     return $this->createModel('Comment')->findAll(['userId' => $this->getId()]);
  }
}

For me, this is very simple to write and understand, but I know many developers are used to config files, annotations and generators nowadays.

from symlex.

If you like this, please contribute 👍

Some pull requests for the documentation would be amazing.

Many things are actually very simple to solve (of course, if you know how, but I can always answer questions). Sorry that I can't publish the proprietary code of commercial projects that are using this framework. Also I don't want to make the example too complex.

from symlex.

I'll close this now. Create a new issue or preferably use our chat if you have more questions.

from symlex.