* Subclass factory for JSON path services
* Common methods moved to JSON path class
* should throw error if _getData is not overridden
* Test JSON path factory using chai-as-promised
* Using chai-as-promised in more tests
* JSDoc for json-path
* Error message adopted to JSON and YAML
* Dynamic YAML badge handles YAML with a string
* 'fetch' naming covention
* Strict string validation in error message
* Packagist user/repo must be lowercase
An issue has developed recently where the package name and repo name of the packagist packages have an added requirement of being lowercase. This has broken the Shields.io badge for some of my projects where their repo name has capital letters, and the badges have been automatically added by a script.
* Prettier
* Lowercase user and repo in getPackageName function instead
* Lowercase user/repo in fetch function
* feat: add BaseSvgScraping service impl for GH Actions
* chore: fix GH Actions service test name
* feat: add branch support to GH Actions/Workflows
* chore: fix schema for GH actions
* refactor: update route path per PR discussion
* when the service responds with only warnings the spec is valid
* add transform method, move color selection to render
* replace forEach with every
* move file extension to query param
* add spec not found, moved url to query param, updated version of supported swagger, WIP redirector
* fix typo
* fix json redirect, add live tests, add redirecter tests
* fix naming, remove mocked test where live one exist
* Added Go version badge
* Using destructuring assignment
* Allowing a client to specify a filename
* Turned a test to live one
* Added golang to keywords
* Renamed parseContent to transform
* Added an example with branch and filename
* Add GitLab pipline suggestion
Added a suggestion for a pipeline badge when a GitLab URL is entered.
* Add tests
Added tests for the GitLab badge suggestion.
* Fix tests
Fixed the tests.
* Add W3C Markup Validation Service Badge (#3833)
* Move helper functions into different file and added unit tests
* Remove unnecessary comments from spec file
* pr changes move code into transform method and validation of messages
* use joi.string().regex instead of custom validator
* Simplify the fetch, handle methods. Make Joi validation for string
* Remove empty parameter from tests and label from render method
* encodeUri on the doc and schema properties send to API
* Documentation and remove unnecessary Object.keys call
* Use regular expressions to make tests less brittle
* made service less for message and color more generic and less brittle
* Throw standard NoFound exception for invalid URL. Use w3c endpoint
* use sazerac for w3c-validation-helper.spec.js
* Replace documentation API url and API documentation url
* Switch back to https://validator.nu endpoint. Remove html4 assertions
* Increase strictness of NotFound checks
* Add documentation for publicity state of pipelines
* Modify visual picture to be smaller and add red circle to mark important setting
* Adapt suggestion
Co-Authored-By: Caleb Cartwright <calebcartwright@users.noreply.github.com>
* Support XPath query with type convertion
* Support XPath query with node function
* Parametrized tests for transform function
* Handle unusual values returned by 'select'
* fix: support scrutinizer branches with only failed builds
* tests: increase timeout for microbadger tests
* tests: increase timeouts for jsdelivr and microbadger tests
While playing around with a badge for Hacktoberfest I noticed the GitHub Issues badge fetches a huge amount of JSON to render just the total count. There doesn’t seem to be a way to limit the response size through the REST API, so I thought I’d switch this to use GraphQL instead.
I recently published https://github.com/metabolize/rq-dashboard-on-heroku and want to add badges to show the locked version of Python and rq-dashboard, the main dependency it’s wrapping.
This is along the lines of #2259, which was for package.json-based applications, and also included some discussion of a Python application that used `requirements.txt`. It’s useful for showing the pinned version of any dependency in a Python application that uses a lockfile.
In the future, as an alternative to reading Pipfile.lock, I could see expanding this to read Pipfile. However for my purposes I prefer to show the locked dependency, since that’s the version that a user of my package would actually get if they ran it on Heroku.
