dhritzkiv / ampersand-file-drop-view Goto Github PK

View Code? Open in Web Editor NEW

3.0 2.0 1.0 101 KB

Drag-and-drop file view build on ampersand-view, and for use in ampersand-form-view

License: MIT License

JavaScript 100.00%

javascript ampersand ampersand-form dnd

ampersand-file-drop-view's People

Contributors

Stargazers

Watchers

Forkers

nubs

ampersand-file-drop-view's Issues

An in-range update of browserify is breaking the build 🚨

The devDependency browserify was updated from `16.3.0` to `16.4.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

browserify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 5 commits.

8980670 16.4.0
f871a85 Update changelog.markdown
52de2c4 Merge pull request #1916 from browserify/stream-http
5dc1bf2 Upgrade stream-http to v3
4a5ea7e Add funding.yml

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Add `reset` method

When ampersand-form-view calls reset, this should reset its state to its original value, which probably requires storing the original value. Alternatively, this view could just call clear

Remove preview functionality

Preview functionality (via FileReader) is not an essential part of this module, therefore it can be removed. Previews can be implemented by extending functionality.

Achieve ampersand-view compliance

In order to achieve ampersand-view compliance, the following errors need to be addressed:

✖ has `setValue` method
✖ should not error when setting valid value
✖ should have called `update` on parent when value changed
✖ should have passed itself to the parent when changed
✖ has `setValue` method after setting a value
✖ should have maintained its value

I'm not entirely sure this can be addressed, as setting value on a file input is possibly not straightforward/doable. However, this can possibly be augmented.

An in-range update of browserify is breaking the build 🚨

Version 14.5.0 of browserify was just published.

Branch	Build failing 🚨
Dependency	browserify
Current Version	14.4.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 9 commits.

ccc0213 14.5.0
f2e720a changelog 14.5.0
37bd7b4 Merge pull request #1733 from dignifiedquire/patch-1
5a0c9ac use ~ range for <v1.0 deps
866a2e7 Merge pull request #1767 from amiller-gh/master
9857f90 Update os-browserify to 0.3.0
0305b70 update readme links and travis badge
9bc05a3 code of conduct
52c0856 bump browserify-zlib to 0.2.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of jshint is breaking the build 🚨

The devDependency jshint was updated from `2.10.2` to `2.10.3`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

jshint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for JSHint 2.10.3

2.10.3 (2019-11-04)

Bug Fixes

Allow more escapes with RegExp u flag (5ac5c46)
Correct binding power of AwaitExpression (af04b1e)
Correct interpretation of commas (691dbdc)
Correct restrictions on class method names (f670aeb)
Correctly interpret class method names (82b49c4)
Do not crash on invalid program code (b14acca)
Interpret "object rest" ident as a binding (c0e9a5b)
Relax singleGroups for async functions (c5dcd90)
Tolerate static as class method name (9cb3b20)
Tolerate valid assignments (0a60c9e)
Validate lone arrow function parameter (38285cd)

Commits

The new version differs by 36 commits.

c43f4ad v2.10.3
38285cd [[FIX]] Validate lone arrow function parameter
691dbdc [[FIX]] Correct interpretation of commas
e63dbc7 [[CHORE]] Revert parser improvements
d72ce61 [[CHORE]] Improve test coverage for logical NOT
d015657 [[CHORE]] Remove unused internal variable
c81bf3a [[CHORE]] Improve CI configuration (#3415)
5a337a8 [[CHORE]] Optimize case clause tracking
9cb3b20 [[FIX]] Tolerate static as class method name
b14acca [[FIX]] Do not crash on invalid program code
2366c92 [[CHORE]] Improve test coverage for RegExp parsing
5ac5c46 [[FIX]] Allow more escapes with RegExp u flag
0a60c9e [[FIX]] Tolerate valid assignments
e04746b [[TEST]] Ignore "information" messages
a70304d [[TEST]] Do not interpret warning as error

There are 36 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Default to false

Documentation says prop.required defaults to false but it currently defaults to true. One of the two should be updated to reflect the other.

Accept files from dataTransfer property from dnd event

An in-range update of tap-spec is breaking the build 🚨

Version 4.1.2 of tap-spec was just published.

Branch	Build failing 🚨
Dependency	`tap-spec`
Current Version	4.1.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

tap-spec is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 6 commits.

0b3f873 Release 4.1.2
810d5ae Merge pull request #60 from maxlutay/check-asserts-length
484f694 also check for asserts.length
90cb1b8 Merge pull request #51 from vassiliy/feat/mocha_pending_appearance
9160ea1 Format pending specs the same way as Mocha
8ce610d Create LICENSE

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Add tests for tests (testing field validity)

Write a test that tests provided tests based on arbitrary criteria, ensuring that at least one of the tests tests fails.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of tape is breaking the build 🚨

The devDependency tape was updated from `4.11.0` to `4.12.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 9 commits.

42c84d6 v4.12.0
3e0a341 [Deps] update is-regex, string.prototype.trim
ba7e2b2 [Dev Deps] update eslint
f3a5925 [Tests] use shared travis-ci configs
6e94800 [Deps] update deep-equal, glob, object-inspect, resolve, string.prototype.trim
8150c3b [Refactor] use is-regex instead of instanceof RegExp
24487cb add tap-nyc to pretty-reporters
c283615 [New] when the error type is wrong, show the message and stack
44cbbf5 [Tests] add a test for the wrong kind of error

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

dhritzkiv / ampersand-file-drop-view Goto Github PK

ampersand-file-drop-view's People

Contributors

Stargazers

Watchers

Forkers

ampersand-file-drop-view's Issues

The devDependency browserify was updated from 16.3.0 to 16.4.0.

Version 14.5.0 of browserify was just published.

The devDependency jshint was updated from 2.10.2 to 2.10.3.

2.10.3 (2019-11-04)

Bug Fixes

Version 4.1.2 of tap-spec was just published.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

The devDependency tape was updated from 4.11.0 to 4.12.0.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency browserify was updated from `16.3.0` to `16.4.0`.

The devDependency jshint was updated from `2.10.2` to `2.10.3`.

The devDependency tape was updated from `4.11.0` to `4.12.0`.