Markus Unterwaditzer
Markus Unterwaditzer
I've created a new feature request at #887 because I really derailed the issue here. It also clarifies what I think is missing from remoteStorage.js
Where would I define such a type?
It would only replace the `{...}` construction I see in `makeNode`. It's not even a real design change?
Shouldn't that be an issue on the spec?
Then I don't know what you're proposing. I thought you were e.g. talking about the `@context` value of folder listings.
I still don't get what you're trying to say :D On Fri, Oct 16, 2015 at 05:27:11AM -0700, Sebastian Kippe wrote: > No, the value of the objects. > >...
> You don't need to release 1.0 for this: semver states that API changes are freely allowed in 0.X.Y That's only half of the story: Yes, API changes are allowed,...
I don't think we can apply this to Python packages. I've seen many packages that follow semver in every sense, except they start to maintain backwards compat from 0.x on.
In terms of API "correctness" I think there's nothing wrong with providing shortcuts. The problem I see (in the long run) is purely from a performance perspective. I.e. if Python...
> We can also start issuing DeprecationWarnings (probably through subclassing) I don't think that's a good idea, you would get different objects when importing from the new vs the old...