Weekly GitHub Report for Fatfree-core - 2024-10-28 12:00:40

Weekly GitHub Report for Fatfree-core

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

---

I. Issues

1.1 Open Issues

Open Issues This Week: 0

Summarized Issues:

As of our latest update, there are no open issues for the project this week.

1.2 Top 5 Active Issues:

We consider active issues to be issues that have generated much discussion in the issue's comments.

1. cannot use data mapper with property named "status": This issue describes a problem where a property named "status" cannot be correctly set using a data mapper in a PHP application with F3 v3.8.1 and PHP v8.2. The user reports that while the property can be set using the set method, directly assigning a value to $object->status results in an anonymous property being added instead of updating the actual database field.

   • The first comment explains that "STATUS" is a reserved keyword in MySQL and provides documentation links, while the second comment clarifies that the user is using PostgreSQL, where "status" is not a reserved keyword, and questions if the framework should handle quoting the identifier.
   • Number of comments: 2

2. Suggestion for internal hive key to prevent collisions: This issue highlights a collision between an internal F3 hive key and a user-defined parameter key, causing a 500 error without debug information. The user suggests prefixing internal hive keys with "_F3__" to prevent such collisions and improve ease of use.

   • The first comment advises reading the Naming Rules in the documentation, suggesting the use of lowercase or camelCase for user-defined variables to avoid conflicts. The second comment acknowledges this advice and expresses intent to be more careful when defining global variables.
   • Number of comments: 2

3. V4 Session Doesn't Passed Between Pages/Routes: This issue describes a problem where session data is not being passed between pages or routes in version 4 of the Fat-Free Framework (F3). The provided test case demonstrates that session variables set in one function are not accessible in another, despite the session appearing correct in Chrome's inspection tools.

   • The first comment suggests not calling new Session() and setting session.auto_start = 1 in php.ini as a workaround, noting that sessions are lost across different storage methods. The second comment proposes a code change in base.php to flip the hive assignment, which temporarily resolves the issue without observed side effects.
   • Number of comments: 2

4. [Bug] \Cache->exists() returns always bool(false) when DSN is folder: This issue describes a bug in the Fat-Free Core framework where the \Cache->exists() method always returns bool(false) when the Data Source Name (DSN) is a folder. The problem arises because slashes and backslashes are stripped in the set() function but not in the exists() or clear() functions, leading to inconsistencies when the cache key contains slashes or backslashes.

   • A commenter confirmed experiencing the same issue in their local development environment and noted that several places in the base.php file should pass the filename string to the fixslashes method. They submitted a pull request to modify the cache get method to filter the incoming key similarly to the set method.
   • Number of comments: 1

Since there were fewer than 5 open issues, all of the open issues have been listed above.

1.3 Top 5 Quiet Issues:

We consider quiet issues to be issues that have been opened in this project for the longest time. The team should work together to get these issues resolved and closed as soon as possible.

1. cannot use data mapper with property named "status": This issue describes a problem where a property named "status" cannot be correctly set using a data mapper in the F3 framework with PHP v8.2. The user reports that while attempting to set the "status" property directly, it creates an anonymous property instead of updating the actual database field, suggesting that "status" might be a reserved keyword.

   • Open for 347 days, 00 hours, 17 minutes

2. Suggestion for internal hive key to prevent collisions: This issue highlights a collision problem between internal F3 hive keys and user-defined parameter keys in the v4.x-dev version, which results in a critical ERROR 500 without any debug information. The user suggests prefixing internal hive keys with "_F3__" to prevent such collisions and improve the ease of setting custom parameters, despite potential backward compatibility concerns.

   • Open for 307 days, 03 hours, 33 minutes

3. [Bug] \Cache->exists() returns always bool(false) when DSN is folder: This issue describes a bug in the Fat-Free Core framework where the \Cache->exists() function consistently returns bool(false) when the Data Source Name (DSN) is a folder. The problem arises because the set() function strips slashes and backslashes from the cache key, but the exists() and clear() functions do not, leading to a situation where cache files are created but subsequently not found.

   • Open for 285 days, 11 hours, 55 minutes

4. V4 Session Doesn't Passed Between Pages/Routes: This issue describes a problem where session data is not being passed between pages or routes in version 4 of the Fat-Free Framework (F3). The provided test case demonstrates that while session data is correctly set and cookies are received, the session arrays remain empty when accessed on subsequent pages, a behavior that does not occur in version 3.8 of the framework.

   • Open for 239 days, 13 hours, 59 minutes

5. Space at the end of route in config causes method not allowed: This issue highlights a bug where a trailing space at the end of a route in the configuration file causes a "method not allowed" error. The user is frustrated that the system does not automatically trim the trailing space, leading to significant debugging challenges.

   • Open for 226 days, 02 hours, 51 minutes

1.4 Closed Issues

Closed Issues This Week: 0

Average Issue Close Time (This Week): 0.00 days

Summarized Issues:

As of our latest update, there are no closed issues for the project this week.

1.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open issues within the past week to identify potentially heated exchanges and to maintain a constructive project environment.

As of our last update, there are no open issues with discussions going on within the past week.

---

II. Pull Requests

2.1 Open Pull Requests

Open Pull Requests This Week: 0

Pull Requests:

As of our latest update, there are no open pull requests for the project this week.

2.2 Closed Pull Requests

Closed Pull Requests This Week: 0

Summarized Pull Requests:

As of our latest update, there are no closed pull requests for the project this week.

2.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open pull requests within the past week to identify potentially heated exchanges and to maintain a constructive project environment.

As of our last update, there are no open pull requests with discussions going on within the past week.

---

III. Commits

3.1 Commits

Commits This Week: 0

Summarized Commits:

As of our latest update, there are no commits for the project this week.

---

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, or created at least 1 pull request in the past month.

As of our latest update, there are no active contributors for the project this week.