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
What we're doing internally is just using a bunch of plugins. We should make this more transparent and remove the obscure options like parse, raw, etc. and replace with { use: [popsicle.use.default] } or similar.
Note: This is a major breaking change and will bump the library to 1.0. I believe the current API is highly stable and useful right now, especially once this gets fixed (it was the only awkward API left).
The text was updated successfully, but these errors were encountered:
* Overridable transportation layer
* Request method short-hands
* Dedicated `options` object for environments and transportation layer to use
* Defaults function for creating Popsicle instances
* Promises resolve on `nextTick`
* Separated browser and node scripts result in a smaller build and better environment detection
Closes#14, #15, #16, #17, #18 and #19. Boom!
* Overridable transportation layer
* Request method short-hands
* Dedicated `options` object for environments and transportation layer to use
* Defaults function for creating Popsicle instances
* Promises resolve on `nextTick`
* Separated browser and node scripts result in a smaller build and better environment detection
Closes#14, #15, #16, #17, #18 and #19. Boom!
* Overridable transportation layer
* Request method short-hands
* Dedicated `options` object for environments and transportation layer to use
* Defaults function for creating Popsicle instances
* Promises resolve on `nextTick`
* Separated browser and node scripts result in a smaller build and better environment detection
Closes#14, #15, #16, #17, #18 and #19. Boom!
What we're doing internally is just using a bunch of plugins. We should make this more transparent and remove the obscure options like
parse
,raw
, etc. and replace with{ use: [popsicle.use.default] }
or similar.Note: This is a major breaking change and will bump the library to
1.0
. I believe the current API is highly stable and useful right now, especially once this gets fixed (it was the only awkward API left).The text was updated successfully, but these errors were encountered: