You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aliases are added, but documentation is not updated
bidders get removed in a major version, but have no prebid version indicator
case sensitivity
🎯 Goal
Reviewers or contributors get automated help if a change breaks documentation.
prebid docs meta data
There are a couple of meta data fields that provide solutions for common problems
filename if biddercode and the actual bid adapter filename, don't match. incrementx.md example
pbjs_version_notes - add text description about prebid version availability iqm.md example
🗒️ Requirements
A propose solution should work for all prebid projects (js, server, app), but does not need to be implemented for all of them.
💡 Ideas
The docs committee thought about github workflows that could be triggered for every pull request. Depending on the repository, the logic could be adapted.
An alternativ would be an external job that regularly checks if stuff is in sync and spit out warnings somewhere.
I recommend extracting all relevant metadata into a new repo. Instead of say aliases being repeated in js, server, docs, etc; have them in one place and make all the others take them from there during build. Let's not: add an Nth new project used for github checks that also needs to be updated on every metadata update.
This repository hosts the documentation for all those projects:
Keeping the documentation in sync with the latest releases is non-trivial.
🎯 Goal
Reviewers or contributors get automated help if a change breaks documentation.
prebid docs meta data
There are a couple of meta data fields that provide solutions for common problems
filename
ifbiddercode
and the actual bid adapter filename, don't match. incrementx.md examplepbjs_version_notes
- add text description about prebid version availability iqm.md example🗒️ Requirements
A propose solution should work for all prebid projects (js, server, app), but does not need to be implemented for all of them.
💡 Ideas
The docs committee thought about github workflows that could be triggered for every pull request. Depending on the repository, the logic could be adapted.
An alternativ would be an external job that regularly checks if stuff is in sync and spit out warnings somewhere.
🔗 Relates issues
The text was updated successfully, but these errors were encountered: