Browse files

Append .html to links.

  • Loading branch information...
1 parent 2d58e71 commit d44ea8556580ace889a65bb9961b645477c1664b @postmodern postmodern committed Aug 4, 2011
Showing with 30 additions and 30 deletions.
  1. +1 −1
  2. +1 −1
  3. +3 −3 docs/dm_more/
  4. +1 −1 docs/dm_more/
  5. +11 −11 docs/
  6. +1 −1 docs/
  7. +1 −1 docs/
  8. +7 −7
  9. +4 −4
@@ -13,7 +13,7 @@ Links, Blogs, Wiki's, and Stuff
- <dt><a href="/news">News and Notes</a></dt>
+ <dt><a href="/news.html">News and Notes</a></dt>
<dd>Official News and other contributed articles</dd>
<dt><a href="">Wiki</a></dt>
@@ -34,7 +34,7 @@ Git - Edge DataMapper
DataMapper development uses [Git]( SCM.
-Please see [using git](/using-git) to learn how to contribute.
+Please see [using git](/using-git.html) to learn how to contribute.
For detailed instructions how to get a proper development setup for
datamapper up and running, have a look at the [edge guide](
@@ -32,20 +32,20 @@ validations based on the properties specified and also allows assignment of
manual validations. It also supports contextual validation, allowing a resource
to be considered valid for some purposes but not others.
-### [dm-timestamps](/docs/dm_more/timestamps)
+### [dm-timestamps](/docs/dm_more/timestamps.html)
This defines callbacks on the common timestamp properties, making them
auto-update when the models are created or updated. The targeted properties are
`:created_at` and `:updated_at` for DateTime properties and `:created_on` and
`:updated_on` for Date properties.
-### [dm-aggregates](/docs/dm_more/dm-aggregates)
+### [dm-aggregates](/docs/dm_more/dm-aggregates.html)
This provides methods for database calls to aggregate functions such as `count`,
`sum`, `avg`, `max` and `min`. These aggregate functions are added to both
collections and Models.
-### [dm-types](/docs/dm_more/types)
+### [dm-types](/docs/dm_more/types.html)
This provides several more allowable property types. `Enum` and `Flag` allow a
field to take a few set values. `URI`, `FilePath`, `Regexp`, `EpochTime` and
@@ -19,7 +19,7 @@ no matter what the ruby object is, or which data-store is used as the backend.
-In [DM More](/docs/dm_more) there is the dm-types gem, which supplies several
+In [DM More](/docs/dm_more/) there is the dm-types gem, which supplies several
more types that map less common ruby classes to data-store values or take care
of serializing them to text based formats.
@@ -11,27 +11,27 @@ created_at: Fri Nov 30 15:29:01 +1030 2007
<dt><a href="">API</a></dt>
<dd>The API for the current gem release.</dd>
- <dt><a href="/why">Why DataMapper?</a></dt>
+ <dt><a href="/why.html">Why DataMapper?</a></dt>
<dd>If you haven't read this yet, you should, right now!</dd>
- <dt><a href="/getting-started">Getting Started</a></dt>
+ <dt><a href="/getting-started.html">Getting Started</a></dt>
<dd>A whirlwind tour of DM. This is the place to start if you haven't used the library before.</dd>
- <dt><a href="/docs/install">Common installation issues</a></dt>
+ <dt><a href="/docs/install.html">Common installation issues</a></dt>
<dd>Troubleshooting installation, with instructions for specific platforms.</dd>
- <dt><a href="/docs/properties">Properties</a></dt>
+ <dt><a href="/docs/properties.html">Properties</a></dt>
<dd>Properties declared in your model map to the fields in the database.</dd>
- <dt><a href="/docs/create_and_destroy">Creating, Saving, Updating and Destroying Records</a></dt>
+ <dt><a href="/docs/create_and_destroy.html">Creating, Saving, Updating and Destroying Records</a></dt>
<dd>Obviously you're going to be doing a lot of this :)</dd>
- <dt><a href="/docs/validations">Validations</a></dt>
+ <dt><a href="/docs/validations.html">Validations</a></dt>
<dd>Auto-validations, manual validations, contextual validations</dd>
- <dt><a href="/docs/find">Finding and Counting Records</a></dt>
+ <dt><a href="/docs/find.html">Finding and Counting Records</a></dt>
<dd>There are lots of nice ways to find records.</dd>
- <dt><a href="/docs/associations">Associations</a></dt>
+ <dt><a href="/docs/associations.html">Associations</a></dt>
<dd>Models can be associated to each other in various ways using the <code>has</code> keyword</dd>
- <dt><a href="/docs/callbacks">Hooks</a></dt>
+ <dt><a href="/docs/callbacks.html">Hooks</a></dt>
<dd>Hooks, AKA Callbacks, allow you to "advise other methods" by running methods before or after calling other methods.</dd>
- <dt><a href="/docs/misc">Misc. Features</a></dt>
+ <dt><a href="/docs/misc.html">Misc. Features</a></dt>
<dd>Paranoia, Timezone Handling, Single Table Inheritance, and Multiple Repositories.</dd>
- <dt><a href="/docs/legacy">Working with Legacy Schemas</a></dt>
+ <dt><a href="/docs/legacy.html">Working with Legacy Schemas</a></dt>
<dd>Adapting data-store naming conventions to your own property names.</dd>
<dt><a href="/docs/dm_more/">More</a></dt>
<dd>Plugins galore for DataMapper.</dd>
@@ -8,7 +8,7 @@ created_at: Tue Dec 04 13:20:00 +1030 2007
{{ page.title }}
-If you've followed the [install instructions](/getting-started) but run
+If you've followed the [install instructions](/getting-started.html) but run
into problems, you can find some tips below.
@@ -72,7 +72,7 @@ Multiple Data-Store Connections
DataMapper sports a concept called a context which encapsulates the data-store
context in which you want operations to occur. For example, when you setup a
-connection in [getting-started](/getting-started), you were defining a
+connection in [getting-started](/getting-started.html), you were defining a
context known as `:default`
{% highlight ruby linenos %}
@@ -137,7 +137,7 @@ You need to make sure to do this before you use your models, i.e. before you act
**Note**: that currently you **must** setup a `:default` repository to work
with DataMapper (and to be able to [use additional differently named
-repositories](/docs/misc)). This might change in the future.
+repositories](/docs/misc.html)). This might change in the future.
Define your models
@@ -177,16 +177,16 @@ end
The above example is simplified, but you can also specify more options such as
constraints for your properties. DataMapper supports a lot of different
-[property](/docs/properties) types natively, and more through
+[property](/docs/properties.html) types natively, and more through
An important thing to note is that every model *must* have a key in
order to be valid. If a model has no key, there's no way to identify a
resource and thus no way to update its persistent state within the
backend datastore. DataMapper will raise a `DataMapper::IncompleteModelError`
when trying to `auto_migrate!` a model that has no key declared.
-Have a look at [property](/docs/properties) to learn about the different
+Have a look at [property](/docs/properties.html) to learn about the different
ways of declaring keys for your models.
@@ -199,7 +199,7 @@ re-open the classes.
### One To Many
Posts can have comments, so we’ll need to setup a simple
-[one-to-many](/docs/associations#has_n_and_belongs_to_or_onetomany) association
+[one-to-many](/docs/associations.html#has_n_and_belongs_to_or_onetomany) association
between then:
{% highlight ruby %}
@@ -216,7 +216,7 @@ end
Has and belongs to many Categories can have many Posts and Posts can have many
Categories, so we’ll need a
-[many to many](/docs/associations#has_n_through_or_onetomanythrough) relationships
+[many to many](/docs/associations.html#has_n_through_or_onetomanythrough) relationships
commonly referred to “has and belongs to many”. We’ll setup a quick model to
wrap our join table between the two so that we can record a little bit of
meta-data about when the post was categorized into a category.
@@ -310,7 +310,7 @@ also can be used on an individual model (e.g. `Post.auto_migrate!`)
Create your first resource
-Using DataMapper to [create](/docs/create_and_destroy#creating) a resource (A
+Using DataMapper to [create](/docs/create_and_destroy.html#creating) a resource (A
resource is an instance of a model) is simple
{% highlight ruby %}
@@ -32,7 +32,7 @@ develop independently of your models using Migrations.
To support data-stores which you don't have the ability to manage yourself, it's
simply a matter of telling DataMapper where to look. This makes DataMapper
-a good choice when [Working with legacy databases](/docs/legacy)
+a good choice when [Working with legacy databases](/docs/legacy.html)
{% highlight ruby linenos %}
class Post
@@ -266,14 +266,14 @@ this limitations by using DataMapper's feature that allows you to query
models by their associations, as described briefly in the chapter below.
You can also find more information about this feature on the
-[Finders](/docs/find) and the [Associations](/docs/associations) pages.
+[Finders](/docs/find.html) and the [Associations](/docs/associations.html) pages.
Querying models by their associations
DataMapper allows you to create and search for any complex object graph simply by providing a nested hash of conditions. The following example uses a typical Customer - Order domain model to illustrate how nested conditions can be used to both create and query models by their associations.
-For a complete definition of the Customer - Order domain models have a look at the [Finders](/docs/find) page.
+For a complete definition of the Customer - Order domain models have a look at the [Finders](/docs/find.html) page.
{% highlight ruby linenos %}
# A hash specifying one customer with one order
@@ -326,7 +326,7 @@ Customer.all( => "%BLUE%")
{% endhighlight %}
You can even chain calls to `all` or `first` to continue refining your query or
-search within a scope. See [Finders](/docs/find) for more information.
+search within a scope. See [Finders](/docs/find.html) for more information.
Identity Map

0 comments on commit d44ea85

Please sign in to comment.