search

nth-cloud / ng-mentions

Rich Mentions Component for Angular
http://nth-cloud.github.io/ng-mentions
MIT License
12 stars 12 forks source link

multiple mention triggerChar and mentions configuration #42

Closed Gray-Simon closed 1 year ago

Gray-Simon commented 2 years ago

Please remember, the issues forum is NOT for support requests. It is for bugs and feature requests only. Please search existing issues (both open and closed) prior to opening any new issue and ensure you follow the instructions therein.

Bug description: is it possible we have multiple mention configuration with each configuration having their specific triggerCharacter and mentions object e.t.c

for example: supporting '#'(hastag) and '@'(mention) on the same directives. then their will be a configuration array on the component file: { cols: 3; rows:12; dropUp: true, sear mentionConfig: [ { triggerChar: '@', mentions: any[], }, { triggerChar: '#', mentions: any[] } ] }

Link to minimally-working plunker that reproduces the issue:

You can fork a plunker from one of our demos and use it as a starting point. Please note that we can not act on bug reports without a minimal reproduction scenario in plunker.

Version of Angular and ng-mentions:

Angular:

ng-mentions:

trickeyone commented 2 years ago

@Gray-Simon As I said in my response to your other ticket (https://github.com/nth-cloud/ng-mentions/issues/41#issuecomment-1205803234), it's not currently possible and would take a decent rework to make it possible. If you want to take a crack at it, please feel free to submit a pull request. I don't currently have the bandwidth to do so with my regular job workload. If you don't mind waiting for a few months, I could try to have something by the end of the year.

stale[bot] commented 2 years ago

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 24 hours. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again!