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
I don't want to describe a particular solution, but I was thinking that each page could be linked to a label of open issues to look through? We already have the package: babel-core field on a lot of doc pages that we could use?
The text was updated successfully, but these errors were encountered:
What will we want to achieve in the end of this? For what I can understand 2 routes can be taken in here depending on the community ideas:
Simply always show the link to a certain label using the existing package field as proposed, even when there are no issues at all assigned to that label.
Hook up to github API, get all the issues, store them as an object by label. If there are any issues with a combo of page label connection + help wanted show the warning and the link to the those issues.
Simply always show the link to a certain label using the existing package field as proposed, even when there are no issues at all assigned to that label.
This seems to be easy to implement. We can have a property in the layout and map the property with the Github issue.
Hook up to github API, get all the issues, store them as an object by label. If there are any issues with a combo of page label connection + help wanted show the warning and the link to the those issues.
I don't think we can implement this, because we've API rate limiting so it will be stable all time.
Ref https://twitter.com/avanslaars/status/923906843704987649
I don't want to describe a particular solution, but I was thinking that each page could be linked to a label of open issues to look through? We already have the
package: babel-core
field on a lot of doc pages that we could use?The text was updated successfully, but these errors were encountered: