Skip to content

Commit f315b4b

Browse files
authored
Merge pull request #1433 from tacman/patch-2
Update usage.md, use 'attribute' not annotation
2 parents f21f620 + 32592ac commit f315b4b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/usage.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -48,10 +48,10 @@ want to make uploadable.
4848
4949
We already created an abstract representation of the filesystem (the mapping),
5050
so we just have to tell the bundle which entity should use which mapping. In
51-
this guide we'll use annotations to achieve this, but you can also use
51+
this guide we'll use attributes to achieve this, but you can also use
5252
[YAML](mapping/yaml.md) or [XML](mapping/xml.md).
5353
54-
First, annotate your class with the `Uploadable` annotation. This is really like
54+
First, annotate your class with the `Uploadable` attribute. This is really like
5555
a flag indicating that the entity contains uploadable fields.
5656

5757
Next, you have to create the two fields needed for the bundle to work:
@@ -62,7 +62,7 @@ Next, you have to create the two fields needed for the bundle to work:
6262
object after the form is submitted. This should *not* be persisted to the
6363
database, but you *do* need to annotate it.
6464

65-
The `UploadableField` annotation has a few options. They are as follows:
65+
The `UploadableField` attribute has a few options. They are as follows:
6666

6767
* `mapping`: required, the mapping name specified in the bundle configuration to use;
6868
* `fileNameProperty`: required, the property that will contain the name of the uploaded file;

0 commit comments

Comments
 (0)