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'm not sure if a "UI for writing x-bte annotations" discussions / dev work needs to wait for x-bte refactoring work to be further along....or if it depends on other work for other issues like #522 and #707
This came up in old discussions between Jackson and me (and during our in-person week in April/May)...
A UI for writing x-bte annotations would be helpful. Some features could be:
have the basic structure of the x-bte operation to fill out
as the writer makes the list of x-bte references for the endpoint (ex), autopopulate info in the components section (like operation names, basic structure to fill out)
maybe vice-versa? If the writer starts writing the full x-bte info in the components section first, automatically start making the list of x-bte references to put under the endpoint? (I'm not sure how this'll work on rethink, since we don't necessarily know which endpoint to put the references under)
The text was updated successfully, but these errors were encountered:
I'm not sure if a "UI for writing x-bte annotations" discussions / dev work needs to wait for x-bte refactoring work to be further along....or if it depends on other work for other issues like #522 and #707
This came up in old discussions between Jackson and me (and during our in-person week in April/May)...
A UI for writing x-bte annotations would be helpful. Some features could be:
The text was updated successfully, but these errors were encountered: