michaelbromley / michaelbromley/angularUtils
dirPagination cannot be compile in other directive
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2k
- Forks
- 842
- PR merge metrics
- No merged PRs in 30d
Description
Hi, thanks for contributing!
This project is maintained in my spare time, so in order to help me address your issue as quickly as
possible, please provide as much of the following information as you can:
- Title: Please indicate the module in question, e.g. "dirPagination: X is broken when Y"
- If reporting on dirPagination, please include the version you are using (can be found in the package.json / bower.json file)
- If you are able to reproduce your issue on Plunker, this will vastly increase the chances of a rapid response from me.
-- Michael
(Delete the above. Fill in the rest as applicable)
Description of issue:
i compile(*temp)(scope) in my directive link fn.
*temp have complete dir-Pagination that's all right.
Steps to reproduce:
i compile(*temp)(scope) in my directive link fn.
*temp have complete dir-Pagination that's all right.
Expected result:
compile show the dir-Pagination in controller
Actual result:
my directive link not executed
Demo: (for dirPagination, fork and modify this Plunk: http://plnkr.co/edit/b37IdFFJUokaeSummETX?p=preview)
Any relevant code:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the linked Plunker, using the directive link function and the dynamically compiled template containing dirPagination. Inspect why the directive's link function is not executed when compile(*temp)(scope) is used. Done means dirPagination compiles inside the other directive and the expected controller output appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100