DDC-823: Errors in 2.0 Cookbook Documentation #1015

Closed
opened 2026-01-22 12:59:00 +01:00 by admin · 5 comments
Owner

Originally created by @doctrinebot on GitHub (Oct 1, 2010).

Originally assigned to: @guilhermeblanco on GitHub.

Jira issue originally created by user ralfas:

http://www.doctrine-project.org/projects/orm/2.0/docs/cookbook/getting-started-xml-edition/en#getting-started-xml-edition

Paragraph 1:
The benefit of Doctrine for the programmer is the possibility -can- to focus -soley- solely on the business and worry about persistence only as a secondary task. This doesn't mean persistence is not important to Doctrine 2, however it is our belief that there are considerable benefits for object-oriented programming, if persistence and entities are kept perfectly -seperated- separated.

Paragraph 2:
Entities are -leightweight- lightweight PHP Objects that don't need to extend any abstract base class or interface. An entity class must not be final or contain final methods. Additionally it must not implement __clone nor __wakeup or it should do so safely.

What would be the best way to note other errors?

Originally created by @doctrinebot on GitHub (Oct 1, 2010). Originally assigned to: @guilhermeblanco on GitHub. Jira issue originally created by user ralfas: http://www.doctrine-project.org/projects/orm/2.0/docs/cookbook/getting-started-xml-edition/en#getting-started-xml-edition Paragraph 1: The benefit of Doctrine for the programmer is the possibility -can- <ins>to</ins> focus -soley- <ins>solely</ins> on the business and worry about persistence only as a secondary task. This doesn't mean persistence is not important to Doctrine 2, however it is our belief that there are considerable benefits for object-oriented programming, if persistence and entities are kept perfectly -seperated- <ins>separated</ins>. Paragraph 2: Entities are -leightweight- <ins>lightweight</ins> PHP Objects that don't need to extend any abstract base class or interface. An entity class must not be final or contain final methods. Additionally it must not implement __clone nor __wakeup or <ins>it should</ins> do so safely. What would be the best way to note other errors?
admin closed this issue 2026-01-22 12:59:00 +01:00
Author
Owner

@doctrinebot commented on GitHub (Oct 4, 2010):

Comment created by @beberlei:

The best way for us would be if you fork the docs on github, change the stuff and commit it. Then issue a pull request. It sounds complicated, but should be minimal overhead of ~5 minutesn on your end, but then we can merge it with a mouse-click, so we dont need to duplicate the whole correction effort on our end.

@doctrinebot commented on GitHub (Oct 4, 2010): Comment created by @beberlei: The best way for us would be if you fork the docs on github, change the stuff and commit it. Then issue a pull request. It sounds complicated, but should be minimal overhead of ~5 minutesn on your end, but then we can merge it with a mouse-click, so we dont need to duplicate the whole correction effort on our end.
Author
Owner

@doctrinebot commented on GitHub (Jan 27, 2011):

Comment created by jclermont:

I have fixed the typos from this ticket that were still present in the docs and issued a pull request on Github.

@doctrinebot commented on GitHub (Jan 27, 2011): Comment created by jclermont: I have fixed the typos from this ticket that were still present in the docs and issued a pull request on Github.
Author
Owner

@doctrinebot commented on GitHub (Jul 11, 2011):

Comment created by mridgway:

This issue should be closed: https://github.com/doctrine/orm-documentation/pull/17

@doctrinebot commented on GitHub (Jul 11, 2011): Comment created by mridgway: This issue should be closed: https://github.com/doctrine/orm-documentation/pull/17
Author
Owner

@doctrinebot commented on GitHub (Apr 18, 2014):

Comment created by @guilhermeblanco:

Issue got fixed somehow in the past

@doctrinebot commented on GitHub (Apr 18, 2014): Comment created by @guilhermeblanco: Issue got fixed somehow in the past
Author
Owner

@doctrinebot commented on GitHub (Apr 18, 2014):

Issue was closed with resolution "Fixed"

@doctrinebot commented on GitHub (Apr 18, 2014): Issue was closed with resolution "Fixed"
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#1015