Skip to content
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

Adding Deprecation links #556

Merged
merged 3 commits into from
Mar 17, 2015

Conversation

jamiehannaford
Copy link
Contributor

Note: this PR depends on #555 being merged first. We also need to setup docs.php-opencloud.com CNAME (or whatever the subdomain will be) first. I've just noticed that I've referenced doc.* - so I'll need to do a search and replace and rebase

## 5. Other functionality

For a full list of functionality provided by Guzzle, please consult the [official documentation](http://docs.guzzlephp.org/en/latest/http-client/client.html).
https://doc.php-opencloud.com/en/latest/index.html
Copy link
Contributor

Choose a reason for hiding this comment

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

Any reason you decided not to have a separate document on Clients in the new documentation?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought about it, but every service now in its introduction references how to set up the relevant client and service (for both OS and RS). It provides the sample and explains all the arguments in detail, so I didn't think a separate document (that wasn't tied to a specific service) would have much use. What do you think?

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree that a separate, standalone document on setting up OS/RS clients is not useful any more. There are, however, other parts of this document - specifically the parts about User Agents and Loggers - that are not included anywhere else in the new documentation. Do you think we ought to create a separate document (or documents) for them, if we are going to remove this document on Clients?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes, definitely - that was an oversight on my part. I think we should add add them as separate documents and link to them in the "usage tips" toctree in index.rst

Copy link
Contributor

Choose a reason for hiding this comment

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

Sounds good. Do you want to include them in this PR (I would prefer this as the Clients document is being deleted in this PR) or in a separate PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yup, I'll add now and rebase too

@jamiehannaford
Copy link
Contributor Author

@ycombinator ok, I've added some more docs - does that cover everything? We need to set up the CNAME before this PR is merged

@jamiehannaford
Copy link
Contributor Author

@ycombinator The DNS migration is done 🤘 This is ready for review again

@coveralls
Copy link

Coverage Status

Coverage remained the same at 88.28% when pulling 6e699ce on jamiehannaford:deprecation-links into 3dfe7c4 on rackspace:working.

ycombinator added a commit that referenced this pull request Mar 17, 2015
@ycombinator ycombinator merged commit 8105fa1 into rackspace:working Mar 17, 2015
@jamiehannaford jamiehannaford deleted the deprecation-links branch March 17, 2015 08:54
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.

None yet

3 participants