clampy-js / ngx-clampy Goto Github PK

I have no problem running ngx-clampy on Angular 7 but npm/yarn is warning about peer dependency.

Hi,

I have a use case that: I put clampy directive on my <p> and upon initializing the component, I want to know if the text in my <p is clamped or not so I can show the link Show more. If the text in my <p> isn't clamped because it doesn't exceed the width of the parent, then I don't want to show that Show more link.

I notice that the event originalContent only fires when the text in p is clamped. Maybe clampy directive can expose an event to notify the users that the text isn't clamped because it doesn't exceed the width of the parent.

I include an example from Stackblitz here

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

There does not seem to be a way to put HTML after the truncation character (such as a link that says Read More)

Input change event is not triggered when changing ng-content from parent hence I tried to pass ng-content data in clampyContent input of directive, here now ellipsis is completely removed.

I have used clampy directive on projected content , when projected contents get updated from parent component it is still showing the same element.innerHTML = initially bound content;
<div clampy>
<ng-content><ng-content>
<div>

<div clampy>
My content h1
<div>

when I change parent component template where nativeElment on which directive is applied is changed:
<div clampy>
My content h1 changed !!
<div>

Element on which directive is applied remains same : My content h1

I gone through the code, seems like el.innerHTML is not getting updated

Here is my stackblitz example : Here is my stackblitz

https://stackblitz.com/edit/angular-znpncy

@alexandremoore , Please have a look

@ahnpnl any idea ?

🚨 The automated release from the 7.0.x branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the 7.0.x branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 1.4.0 on branch 7.0.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=7.0.0 <1.3.4 can be published from branch 7.0.x.

The following commits are responsible for the invalid release:

• fix: fix CI build (dade38f)
• fix: update package-lock.json (ba5277b)
• fix: upgrade semantic-release (054031e)
• feat: Upgrade to Angular 7 (d404cdd)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 7.0.x with git revert or git reset.

A valid branch could be master.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Hi!

Thanks for your work, we are using it daily in our product!

We are actually using Angular 10 now (and preparing 11), and it seems to still work. Do you think we would be able to bump the angular version range up to 11? If so, I would prepare a small PR for that.