Skip to content

Commit

Permalink
Update usage.md, use 'attribute' not annotation
Browse files Browse the repository at this point in the history
  • Loading branch information
tacman authored Feb 15, 2024
1 parent f21f620 commit 32592ac
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,10 +48,10 @@ want to make uploadable.
We already created an abstract representation of the filesystem (the mapping),
so we just have to tell the bundle which entity should use which mapping. In
this guide we'll use annotations to achieve this, but you can also use
this guide we'll use attributes to achieve this, but you can also use
[YAML](mapping/yaml.md) or [XML](mapping/xml.md).
First, annotate your class with the `Uploadable` annotation. This is really like
First, annotate your class with the `Uploadable` attribute. This is really like
a flag indicating that the entity contains uploadable fields.

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

The `UploadableField` annotation has a few options. They are as follows:
The `UploadableField` attribute has a few options. They are as follows:

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

0 comments on commit 32592ac

Please sign in to comment.