Skip to content

Add note about the property attribute (Property Accessor) #3124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from

Conversation

raziel057
Copy link
Contributor

I think we must document the fact that propety is a path which is evaluted by the PropertyAccessor component.

I think we must document the fact that propety is a path which is evaluted by the PropertyAccessor component.
@@ -96,6 +96,23 @@ This is the property that should be used for displaying the entities
as text in the HTML element. If left blank, the entity object will be
cast into a string and so must have a ``__toString()`` method.

Note: ``property`` is the property path used to display the option. So you
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not using a note-directive here?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, make it look like this:

.. note::

The ``property`` option is the property path...

And then everything will start indented by 4 spaces

.. note::

The ``property`` option is the property path used to display the option. So you
can use anything supported by the :doc:`PropertyAccessor component</components/property_access/introduction>`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you should move the doc directive to a new line and add a space between component and the opening angle bracket

can use anything supported by the
:doc:`PropertyAccessor component </components/property_access/introduction>`

Usage sample::
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok then, how about we just tell them what translations looks like here:

For example, if the translations property is actually an associative array of objects, each with a name property, then you could do this::

Then I'm not sure if we need the query_builder option - it may just be distracting.

Thanks for the work on this @raziel057!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ping @raziel057 - what do you think about removing the query_builder option and adding the note above?

Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, I made the change as requested.

@weaverryan
Copy link
Member

Awesome, thanks Thomas! It's definitely a really great note to have in there!

weaverryan added a commit that referenced this pull request Mar 18, 2014
…r) (raziel057)

This PR was submitted for the 2.2 branch but it was merged into the 2.3 branch instead (closes #3124).

Discussion
----------

Add note about the property attribute (Property Accessor)

I think we must document the fact that propety is a path which is evaluted by the PropertyAccessor component.

Commits
-------

46f1b8b Update entity.rst
7496e68 Update entity.rst
c097f9b Update entity.rst
7d65fed Update entity.rst
6af779d Add note about the property attribute (Property Accessor)
@weaverryan weaverryan closed this Mar 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants