Comments (12)
It's a good goal to get a stable release and then maintain release vs. development branches going forward. A lot of point releases have introduced bugs.
Parse::Date is the source of the most bugs/annoyance for us. Feels like a 1.0 requirement to kill that. Posting deltas could be a big performance improvement (and generally saner way to do things) but a big overhaul, might be good as a 1.1 target. Parse::Client might deserve some cleaning up pre-1.0 too, it has some commented out code and sort of a half-attempt at being threadsafe by pulling in a barely used IronMQ dependency. Seems best to ship a non-thread-safe synchronous client with a sane way to use multiple Parse::Client objects throughout an app. Right now everything refers back to @@client but it shouldn't be a huge amount of work to fix that so you can at least pass an optional client into everything. A future release milestone might be to abstract away the network request layer entirely so we're not in charge of network behaviors and retries but instead are just built as a layer on top of one of the HTTP futures frameworks.
from parse-ruby-client.
Maybe we setup github pages for documentation purpose rather then maintain on big README.
Imho in readme there should be only most important things like warnings, not supported or beta features notes etc
@ericcj Did you see #88? Think this is the HTTP abstraction layer which you mentioned.
from parse-ruby-client.
My wishlist for the 1.0 is:
from parse-ruby-client.
Also, documentation (probably with YARD?) somewhere that isn't just the readme. README would be for instructions for development, some quick examples, and a link to common issues in the wiki (which is another thing to start developing).
from parse-ruby-client.
Another thing for 1.0:
- wiki page explaining how to migrate from 0.3.0 to 1.0
- wiki page explaining what's new
from parse-ruby-client.
@rhymes So I was thinking- I think the client change was the only big breaking change we're going to do- a lot of the other changes are features and stuff.
Why don't we go ahead and cut the 1.0.0 release and then have all of the extra, currently missing parse features be minors after that?
Alternatively, we could burn simple tasks like adding features TODO in the readme (such as deleting objets, etc) for a real v1 feeling, then cut the release?
from parse-ruby-client.
@Xavdidtheshadow Yep, we could do that, I feel that before though we should increase the test coverage a bit, review the doc (see also #190), write a changelog (we can use git-extras for that https://github.com/tj/git-extras/blob/master/Commands.md#git-changelog) and some sort of migration guide?
from parse-ruby-client.
Is there an easy place to see where we're missing test coverage on existing code?
Totally. I'll go through tomorrow and make a set of tasks we should actually get ready for 1.0 and when those are done, we can release!
from parse-ruby-client.
@Xavdidtheshadow only locally, I'll enable coveralls later on the repository so we can all see it. Thanks!
from parse-ruby-client.
@Xavdidtheshadow https://coveralls.io/github/adelevie/parse-ruby-client?branch=master here you are :D I also added the badge in the README
from parse-ruby-client.
@rhymes nice! that's way more than I thought it would be- it seems like we're in pretty good shape.
from parse-ruby-client.
yes indeed :)
from parse-ruby-client.
Related Issues (20)
- Why does this require bundler to run? HOT 2
- How to initialize Parse key HOT 3
- Parse Retirement HOT 10
- Can't use github master version HOT 5
- "both URI are relative" when configuring after self-hosted Parse server HOT 4
- unable to create client from console HOT 1
- Google OAuth Configuration
- client key shouldn't be required HOT 3
- Query can end up doing a POST! HOT 10
- Remove support for Ruby 1.9 and 2.0 HOT 4
- Running with local parse server HOT 2
- client.query - error client is undefined method in the contoller HOT 7
- back4app URL HOT 6
- Switch off parse.com HOT 3
- Switch tests to a hosted Parse server
- Multiple Coveralls comments
- Future of this project HOT 2
- Does Parse::Cloud::Function.new Still Work? HOT 2
- user = User.authenticate stopped working HOT 5
- NoMethodError occuered during retry request. HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from parse-ruby-client.