Skip to content
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.

docs(routes): indent the routes example in README #463

Merged
merged 1 commit into from
Nov 21, 2017

Conversation

surajssd
Copy link
Member

Right now the way routes example is explained in it's README, it is
not very helpful and can confuse user, so placing it in right
indentation.

Fixes #402

@surajssd
Copy link
Member Author

@containscafeine @cdrage can you PTAL?

Copy link
Collaborator

@concaf concaf left a comment

Choose a reason for hiding this comment

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

looks fine except a couple of nits


Much like other resource definitions in Kedge, routes have been implemented
by merging `RouteSpec` and `ObjectMeta`, which would mean that you can
define fields like `name` and the rest of the RouteSpec at the same level.

An example would be -
Snippet from [httpd.yml](httpd.yml):
Copy link
Collaborator

Choose a reason for hiding this comment

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

nit: "A" snippet

name: httpd
```

A much detailed example might look like this:
Copy link
Collaborator

Choose a reason for hiding this comment

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

A "more" detailed example ...

Right now the way routes example is explained in it's README, it is
not very helpful and can confuse user, so placing it in right
indentation.
@surajssd
Copy link
Member Author

@containscafeine done!

Copy link
Collaborator

@concaf concaf left a comment

Choose a reason for hiding this comment

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

LGTM, will let @cdrage review and merge

@cdrage
Copy link
Collaborator

cdrage commented Nov 21, 2017

LGTM

@cdrage cdrage merged commit e2c3ed6 into kedgeproject:master Nov 21, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants