After all tests or assertions were deleted the store was not
updated because of the length checks. Now the assertions/tests
will always try to run, to ensure the data is always updated.
I noticed that sometimes the response size is weirdly displayed.
- size `112932` is displayed as `110.28.999999999999996KB`
- size `112990` is displayed as `110.34KB`
The problem is in the decimal calculation. Rounding the value ensure we don't have two `.` in the displayed size.
Also, update the `contributing` to increase the minimum Node version required.
When dragging and dropping items, to delay changing sequence numbers
until after all the resource-dependent logic has completed, we were
relying on the order of children in redux store (which we then converted
into new seq numbers).
This order of children was however not updated when sequence numbers
changed (for example due to file watch changes). This resulted in a
seemingly random drag-and-drop ordering, which in fact was linked to the
initial order when the collection was loaded.
This change sorts all the items by sequence number prior to reordering,
so that those random jumps no longer happen. As this happens on a deep
clone of the collection, no data gets hurt in the process.
fixes#154
- Remove Name tooltip
- Update Folder Name tooltip
- Move Folder Name input under location
- Update Folder Name validation
- Now only allow characters for valid system folder names
- Update label htmlFor ids to input ids
- during the dts transformation, the css import was not recognized, hence marking it as external in the dts transform didn't throw the error
- "extract: true" in postcss plugin makes sure it gets extracted to the final bundle as well
Signed-off-by: Anik Das <anikdas0811@gmail.com>
