Seth Bertalotto
Seth Bertalotto
Thanks for the feedback. The individual module CDN links are located on the Customize page (https://purecss.io/customize/#individual-modules). When you refer to "releases", are you talking about the npm package or something...
Good feedback, so GitHub has the [releases zip file](https://github.com/pure-css/pure/releases/tag/v2.1.0) that they provide when a release is published. I can look at adding the built files into that too.
@lingyan > I like the proposal. Some questions: > > * Can you clarify what goes into `data`? I assume it is post/put body. Yup, that was intended to be...
I'm fine with this approach too, we could flatten it too and just have `params` stay the same and be for the resource parameters. @lingyan @snyamathi thoughts?
Mix of case style is disappointing, might make those all camelcase too.
I like having xhrPath, coresPath and uri being combined, makes it simple without a ton of different options. One question is what if `xhrPath` and `corsPath` need to be different?...
I'm fine with the `meta` data for `registerResource`. I think the original reason for using the CRUD names was to have a clear API for how to use the fetcher...
@pablopalacios Ya its just an implementation detail for the fetchr class.
@roderickhsiao whats the status of this? Also what are your thoughts on introducing hooks?
@roderickhsiao my yearly check-in on this migration work. What is left to be done? Looks like #259 was merged a while ago.