New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release/playful python #129
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ake matcher not care about special ^ char so it can work with non absolute paths, and use | to split parts and not types
Feature/match pipe
…aries on the same parcel were sharing registries (see #109)
… release/playful-python
Feature/parcelhoc updates
…nt parcel types
Unmutable upgrade and logging
…dataparcels into feature/bugfixes
Feature/bugfixes
…lling reducer on a deleted parcel
Feature/delete self marker
allanhortle
approved these changes
Oct 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contains #107 #109 #111 #113 #115 #121 #126 #130
Current pre-release:
v0.16.0-3 npm-tag@next
dataparcels
Parcel.addModifier()
Parcel.addDescendantModifier()
modifyValue
changing type no longer breaks the reducer Bug: modifyValue() calls that change the parcel type break in the reducer #118handleChange
callsParcel._boundarySplit()
was not using_this._treeshare.boundarySplit()
get()
something that cannot beset
Parcel.toConsole()
to log a parcel to the consoleParcel.batchAndReturn
only on top level parcelsbatch()
but returns the parcel instead of callinghandleChange
Parcel.matchPipe()
Parcel.pipe()
but automatically applies the updaters to new parcels whenever they are created and when the providedmatch
rule is matched.matchPipe(match: string, ...updaters: Array<(parcel: Parcel) => Parcel>): Parcel
.
.*
.abc
.*date
.*.*
**.def
.*:Indexed
.*:!Indexed
**:Element
.abc|.def
.
,|
,#
or:
with a preceding%
. e.g.{"dot.key"}
would be matched with.dot%.key
matchPipe
was called.DeletedParcelMarker
now appears as avalue
when the parcel has been marked for deletion. It is a symbol that is exported fromdataparcels
likeimport {DeletedParcelMarker} from "dataparcels"
ParcelTypes
react-dataparcels
ParcelHoc config.initialValue
is now calledParcelHoc config.valueFromProps
ParcelHoc
now usesgetDerivedStateFromProps
. Use https://github.com/reactjs/react-lifecycles-compat if you're on a React version earlier than 16.3.0isFirst()
orisLast()
change Bug: ParcelBoundary pure does not update if isFirst() or isLast() changes #119ParcelBoundary
tests to avoidsetTimeout
or any nestedexpect
calls.ParcelBoundaryHoc
(Add ParcelBoundaryHoc #108)ParcelHoc config.shouldParcelUpdateFromProps
which allows a ParcelHoc to replace its parcel's contents based on prop changes. At this point the only option is to completely replace all of the parcels contents and delete all key and meta information, depending on the outcome of a boolean test. In future there will be more options to allow partial changes, and to allow key and meta data to be retained.ParcelBoundary.actions.cancel()
to be able to cancel changes in a parcel boundaryParcelHoc
config.debugParcel
Add ParcelHoc({debugParcel: true}) #86ParcelBoundary
debugParcel
DeletedParcelMarker
fromdataparcels
dataparcels-docs
ParcelBoundary.childRenderer
docsParcelBoundary.actions.cancel()
to docsParcelBoundaryHoc
docsParcelHoc
andParcelBoundaryHoc
other
dataparcels-plugin-form
package