---
title: "New Feature Request"
version: "5.11"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.phalcon.io/llms.txt
> Use this file to discover all available pages before exploring further.

# New Feature Request

[List of NFRs][new-feature-request-list]

A NFR is a short document explaining how a new feature request must be submitted, how it can be implemented, and how it can help core developers and others to understand and implement it.

A NFR contains:

* Suggested syntax
* Suggested class names and methods
* A description detailing the usage
* How it can benefit the framework and the community
* If the feature is already implemented in other frameworks, a short explanation of how that was implemented and its advantages

In the following cases a new feature request will be rejected **if**:

* The feature makes the framework slow
* The feature does not provide any additional value to the framework
* The NFR is not clear, bad documentation, unclear explanations, etc.
* The NFR has not been discussed with the Team or voted by the community
* The NFR does not follow the current guidelines/philosophy of the framework
* The NFR affects/breaks applications developed in current/older versions of the framework
* The original poster does not provide feedback/input when requested
* It's technically impossible to implement
* It can only be used in the development/testing stages
* Submitted/proposed classes/components don't follow the [Single Responsibility Principle][srp]
* Uses static methods - (not allowed)

To send a NFR you do not need to provide Zephir or C code or develop the feature. New Feature requests explain the goal of the intended implementation and start a discussion on how best to implement it.

All NFRs should be posted as a new issue on [GitHub][issues]. Please make sure to use the prefix `[NFR]` in the title of your issue.

[new-feature-request-list]: /5.11/new-feature-request-list/
[srp]: https://en.wikipedia.org/wiki/Single_responsibility_principle
[issues]: https://github.com/phalcon/cphalcon/issues

Source: https://docs.phalcon.io/5.11/new-feature-request/index.mdx