Skip to content
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

Scroll sensitivity control in each direction #1830

Open
wants to merge 31 commits into
base: master
Choose a base branch
from

Conversation

sebastien-prudhomme
Copy link

Because of a fixed header in my application, i needed to have fine control on scroll sensitivity in the top direction.

Here is the patch i use.

To not break compatibilty i chose to use an object with top, bottom, left and right keys.

waynevanson and others added 28 commits August 7, 2020 15:27
…ortableJS#1875)

* deps: install dev-deps for ts, tests and friends

* tests: replace test.js with test.ts and fp

* change compat tests

* ci: replace tests to use npm as per usual
…1878)

The doc was missing the case of keeping the default insertion point based on the direction.
* refactor(tests): move HTML fixtures into own dir

* refactor(tests): separate e2e tests into folders

* refactor(deps): packagejson reformat

* refactor(deps): remove cypress from dev deps

* refactor(ci): add description to circleci
* refactor(tests): move HTML fixtures into own dir

* refactor(tests): separate e2e tests into folders

* refactor(deps): packagejson reformat

* refactor(deps): remove cypress from dev deps

* refactor(ci): add description to circleci

* build: bundles with rollup ^2.14 and typescript

* dist: create new dist files

* chore: bump minor version

* build(refactor): removes unused babel plugin
* build: upgrade to 1.11.0

* tests(fix): emit exit code 1 on fail
* build: upgrade to 1.11.0

* tests(fix): emit exit code 1 on fail

* refactor: microbundle and typescript

* ci: ensure lerna is globally available

* build: use yarn and workspaces

* use lerna

* build: add private to sortbale repo

* v1.11.1

* ci: use yarn and lerna together

* fix ci

* tests: fix tests
…S#1914)

* refactor: remove code formattings config files

* docs: add more detail to contribution guidelines

* docs: remove custom templates

* docs: update bug report issue

* docs: add discussion template

* docs: update featue template
…-links

Readme invalid hyperlinks corrected
…ableJS#1921)

* refactor: remove code formattings config files

* docs: add more detail to contribution guidelines

* docs: remove custom templates

* docs: update bug report issue

* docs: add discussion template

* docs: update featue template

* fix(build): build dist/sortablejs, was missing prior

* build(deps): yarn upgrade

* v1.11.2-alpha.4
* refactor: remove code formattings config files

* docs: add more detail to contribution guidelines

* docs: remove custom templates

* docs: update bug report issue

* docs: add discussion template

* docs: update featue template

* fix(build): build dist/sortablejs, was missing prior

* build(deps): yarn upgrade

* v1.11.2-alpha.4
* refactor: remove code formattings config files

* docs: add more detail to contribution guidelines

* docs: remove custom templates

* docs: update bug report issue

* docs: add discussion template

* docs: update featue template

* fix(build): build dist/sortablejs, was missing prior

* build(deps): yarn upgrade

* v1.11.2-alpha.4

* fix(build): exports modules correctly

This was broken, visible, and closes SortableJS#1891.
* Create composer.json

* Change project name in composer.json

* Fix authors listed in composer.json

* Update repo source in composer.json

Co-authored-by: Wayne Van Son <[email protected]>

* Update "issues" link in composer.json

Co-authored-by: Wayne Van Son <[email protected]>

* Update homepage link in composer.json

Co-authored-by: Wayne Van Son <[email protected]>

* Update package name in composer.json

Co-authored-by: Wayne Van Son <[email protected]>

* Remove legacy file from composer.json files list

Co-authored-by: Derek DeRaps <[email protected]>
Co-authored-by: Wayne Van Son <[email protected]>
Copy link
Contributor

@waynevanson waynevanson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a nice quality of life change, great work!
We had a repo restructure to a monorepo, so we can't tkae your request as is.

Could you add these changes to the files listed below instead?
The new folder is in packages/plugins/auto-scroll/*

@sebastien-prudhomme
Once you add a commit to staging, you can use git commit --amend, then press in order :,wq to save and quit the editor that pops up.
Then force push with git push -uf origin master

@sebastien-prudhomme
Copy link
Author

@waynevanson I've made the change, just let me more time to test it on my application.

Also can you confirm that there will be no problem with the switch to TypeScript.

@waynevanson
Copy link
Contributor

Also can you confirm that there will be no problem with the switch to TypeScript.

No worries. Please let me know when you're ready.

Also can you confirm that there will be no problem with the switch to TypeScript.

No Problem.

Fix IE11 "SCRIPT16389: Unspecified error." when dragging element

Could not pull in SortableJS#1904 due to merge errors, so this PR was created instead.
@waynevanson waynevanson added the enhancement Quality of life changes to existing features label Sep 25, 2020
@sebastien-prudhomme
Copy link
Author

@waynevanson sorry but i could not manage to test it with the new packaging/typescript way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Quality of life changes to existing features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants