Re: Setting up and accessing a DarkPAN (API docs)

the API link, at the top of MetaCPAN pages, leads to a "YAPC video" which discusses MetaCPAN::API; however, that module's documentation is very clear (using large, bold, block capitals) that it is deprecated and indicates that MetaCPAN::Client should be used instead.

The "API" link at the top of the MetaCPAN pages has https://fastapi.metacpan.org/ as its target. This simply redirects to the API documentation in the github repo. I presume at that point you then followed the "watch the actual talk" link. Instead if you just read the page at github you will see it says

Perhaps the easiest way to get started using MetaCPAN is with MetaCPAN::Client.

which is indeed the current advice AFAIAA. Maybe a short PR to mention that the video (and slides) have been superseded somewhat is all that's needed to clear that up? They are from seven years ago and a lot can change in that time, after all.

Comment on Re: Setting up and accessing a DarkPAN (API docs)

Replies are listed 'Best First'.
Re^2: Setting up and accessing a DarkPAN (API docs) by kcott (Archbishop) on May 07, 2020 at 11:43 UTC
G'day hippo, "The "API" link at the top of the MetaCPAN pages has https://fastapi.metacpan.org/ as its target." Yes, you are correct; however, given that's exactly the same target that I used for the "API" link in the second paragraph of my OP, I don't understand why you thought it necessary to state that. Perhaps I've misunderstood your intent. Just to be clear, the "API" links at the top of MetaCPAN pages and in my OP, both have the same target: https://fastapi.metacpan.org/. The purpose of the three sentences in the second paragraph were: Here's something that's changed which I knew about. Here's something that's changed which I discovered as part of my research. There may be other things that have changed which I don't yet know about — please tell me. "They are from seven years ago and a lot can change in that time, after all." That's sort of my point: a lot can change and I don't know if I'm aware of all changes. "I presume at that point you then followed the "watch the actual talk" link." Yes, that's the "YAPC video" link in my OP. While watching it, I decided to follow along with the MetaCPAN::API documentation to supplement what was being talked about: that's when I discovered the deprecation notice. — Ken	[reply]

Replies are listed 'Best First'.

Re^2: Setting up and accessing a DarkPAN (API docs)
by kcott (Archbishop) on May 07, 2020 at 11:43 UTC

G'day hippo,

"The "API" link at the top of the MetaCPAN pages has https://fastapi.metacpan.org/ as its target."

Yes, you are correct; however, given that's exactly the same target that I used for the "API" link in the second paragraph of my OP, I don't understand why you thought it necessary to state that. Perhaps I've misunderstood your intent. Just to be clear, the "API" links at the top of MetaCPAN pages and in my OP, both have the same target: https://fastapi.metacpan.org/.

The purpose of the three sentences in the second paragraph were:

Here's something that's changed which I knew about.
Here's something that's changed which I discovered as part of my research.
There may be other things that have changed which I don't yet know about — please tell me.

"They are from seven years ago and a lot can change in that time, after all."

That's sort of my point: a lot can change and I don't know if I'm aware of all changes.

"I presume at that point you then followed the "watch the actual talk" link."

Yes, that's the "YAPC video" link in my OP. While watching it, I decided to follow along with the MetaCPAN::API documentation to supplement what was being talked about: that's when I discovered the deprecation notice.

— Ken

[reply]