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
@0candy This is sort of a placeholder/linkpost story to keep track of all leftovers from my work on explorer@2.0. I am assigning it to you as you are the new repo expert. Some of the subtasks have already standalone stories, I think we should eventually get stories created for all subtasks.
For the purpose of Sprint 86 planning, could you please take few of those subtasks that are clear enough from the brief description available here, create new GH issues for them, put these new GH issues to #plan column and provide estimates, so that we can use them on Tuesday for sprint planning?
I think these may be good candidates:
support .model for both accepts & returns
Fix model definition to set schema.title and prevent "Inline model" text in GUI
Consider supporting per-method "produces" and "consumes" configuration
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.
Activity
bajtos commentedon Dec 10, 2015
@0candy This is sort of a placeholder/linkpost story to keep track of all leftovers from my work on explorer@2.0. I am assigning it to you as you are the new repo expert. Some of the subtasks have already standalone stories, I think we should eventually get stories created for all subtasks.
For the purpose of Sprint 86 planning, could you please take few of those subtasks that are clear enough from the brief description available here, create new GH issues for them, put these new GH issues to
#plancolumn and provide estimates, so that we can use them on Tuesday for sprint planning?I think these may be good candidates:
stale commentedon Aug 23, 2017
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale commentedon Sep 6, 2017
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the
CODEOWNERSfile at the top-level of this repository.