Directive outputs missing ((drag) and (dragStart) for agm-marker)
See original GitHub issueIssue description
Only the directive output (dragEnd)
is working for agm-marker
, not (drag)
or (dragStart)
I noticed that in node_modules/@agm/core/directives/marker.d.js
there is only dragEnd: EventEmitter<MouseEvent>;
and not EventEmitters for drag and dragStart although they are in the documentation. Maybe not being compiled properly?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Directive outputs missing ((drag) and (dragStart) for agm ...
I noticed that in node_modules/@agm/core/directives/marker.d.js there is only dragEnd: EventEmitter<MouseEvent>; and not EventEmitters for drag ...
Read more >AgmMarker - @agm/core
This event is fired when the user stops dragging the marker. dragStart. Type : EventEmitter<google.maps.MouseEvent>. Defined in packages/core/ ...
Read more >Create a directive for free dragging in Angular - InDepth.Dev
In this article, we will learn how to create a directive in Angular that ... This will work as drag-start trigger. ... and...
Read more >HTMLElement: dragstart event - Web APIs | MDN
In this example, we have a draggable element inside a container. Try grabbing the element, dragging it, and then releasing it.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I figured it out. I had a difficult time installing this repo because it has failing tests… and I didn’t realize it.
In case anyone has issues with it: Clone the repo, then run
npm install
thennpm run build
and where ever it fails, just comment out the failing tests… so I guess another issue should be opened if not already that:@rapw3k, yes I did. So, any *.spec.ts is a unit test file. Therefore you don’t need it to compile the code. That error is just telling you that you have a failing unit test so you just need to comment them out to get the code to compile. Try commenting out everything
describe('set calculator', () => { ...
see how that works for you.