-
Notifications
You must be signed in to change notification settings - Fork 196
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
Be more lax about resources Meta type #354
Comments
Looks like a fatal error to me, so that stops the tickets updater from running to completion. |
The type constraint should likely allow other keys/values there, and simply validate values for any of the standard keys we constrain on. |
That is, it should be extended to use the |
Can someone patch this please, I'm about to setup a 3rd server, so we'll be getting 3 of these emails a day! |
I'll do it this evening. |
Er, I wasn't recommending MooseX::SlurpyConstructor. See the link to MooseX::Types::Structured above. |
@oalders is this done? |
Not correctly. |
Done enough that we've not mentioned it again - closing |
Does this error stop the whole process, or just skip this doc?
https://github.com/CPAN-API/cpan-api/blob/master/lib/MetaCPAN/Types/Internal.pm#L115
Looks like our "type" doesn't allow
x_
extensions.Should we remove keys matching
qr{\Ax_}i
in the coercion?The text was updated successfully, but these errors were encountered: