RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Mitosis] Angular generator: Remove "on" prefix from EventEmitter outputs

User requests that the Angular generator be updated to remove the "on" prefix from EventEmitter outputs, aligning with Angular's recommended style guide.

Original Source

@@bastiW | 0 pts | 8/26/2024

### I am interested in helping provide a feature! Yes ### Which generators are impacted? - [ ] All - [X] Angular - [ ] HTML - [ ] Qwik - [ ] React - [ ] React-Native - [ ] Solid - [ ] Stencil - [ ] Svelte - [ ] Vue - [ ] Web components ### What problem does this feature solve? Angular strictly recommends not to use prefix "on" on EventEmitters. > Do name events without the prefix on. > Do name event handler methods with the prefix on followed by the event name. > > Why? > This is consistent with built-in events such as button clicks. > > Why? > Angular allows for an [alternative syntax](https://angular.dev/guide/templates/binding) on-*. If the event itself was prefixed with on this would result in an on-onEvent binding expression. > [Rule 05-16: Don't Prefix Output Properties](https://angular.dev/style-guide#style-05-16) This is already resolved when you use a component. The onCancel and onConfirm is changed to cancel and confirm. [

Discussion

Loading comments...