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
Right now it's not really obious which of 40+ API operations of the Blob service REST API are supported within the System App module. I wondered if it might make sense to have an overview page for that (similar to what I initially created in the wiki for the original app).
I think it would even make sense to add at least one additional column, indicating if Unit Tests for that operation exists or another referring to additional remarks for a specific operation. That could make collaboration easier, because you wouldn't have to go through lots of code to see what's already available and what still needs contribution.
What would you think about a (sub-)wiki-page for this kind of overview? I would try to keep it out of the actual repo, to make contributions easier. Or do you think it's not necessary at all?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Right now it's not really obious which of 40+ API operations of the Blob service REST API are supported within the System App module. I wondered if it might make sense to have an overview page for that (similar to what I initially created in the wiki for the original app).
I think it would even make sense to add at least one additional column, indicating if Unit Tests for that operation exists or another referring to additional remarks for a specific operation. That could make collaboration easier, because you wouldn't have to go through lots of code to see what's already available and what still needs contribution.
Having in mind that there might be more APIs to follow (e.g. Queue services REST API with 15+ operations; Table services REST API with 15+ operations; File Services REST API with 35+ operations) it would be a much easier way to get an overview on these things.
What would you think about a (sub-)wiki-page for this kind of overview? I would try to keep it out of the actual repo, to make contributions easier. Or do you think it's not necessary at all?
Looking forward to your feedback!
Beta Was this translation helpful? Give feedback.
All reactions