Comments (10)
ah ok so this is the documentation (I searched for that before creating the PR and couldn't find):
In short, it duplicates the doc in the template for all the "vars".
I'd agree to revert if the doc had types but it seems to me that it only has descriptions (https://github.com/OpenMage/magento-lts/pull/3552/files) so I don't see the point of having a template just for a generic description of multiple constants, which don't even explain what the constant does :-\
eg:
it seems not very useful to me to have a duplicate "names" description for those constants, actually it seems worse than just not having the description at all.
But if people think it's important let's revert it.
from magento-lts.
I don't think there's any value in reverting so I'll not participate, but I'll not oppose, obviously.
edit: actually I think the source is far less readable and it would be so much better to have single comments for every const/variable, but with proper description/typing, otherwise what's the point.
from magento-lts.
Does OpenMage/Magento have a public phpDocumentor archive or why is that important to keep?
from magento-lts.
The arguments offered are in favor of a revert. I have no idea how useful will be those comments in the future.
from magento-lts.
The arguments offered are in favor of a revert. I have no idea how useful will be those comments in the future.
@ADDISON74 actually I said the opposite 😅 and from the emoj reaction I think @elidrissidev agree. @pquerner just asked a question. so let's see if somebody else participates in the discussion.
from magento-lts.
I do not oppose reverting the PR as @sreichel's point is completely valid, but the comments that were removed are not adding much value anyways and the description of the constants as well as their type can be easily inferred from their names. Anyways I'll approve it if someone creates it.
from magento-lts.
What I see its a functionality to copy comments onto multiple variables? My first question would be, is it supported by phpstan for type informations? (or phpstorm?)
But even then I would prefer not having it, as its an uncommon notation many will not understand the meaning of.
But it means we would need to modify the changed files again, as we lost some type and some deprecated annotations (which were intended for multiple entries.
And its a bit odd to have the comments in plural, when the comment is copied into each entry.
Its also documented in their code, although not in their documentation https://github.com/phpDocumentor/ReflectionDocBlock/blob/7b217217725dc991a0ae7b995041cee1d5019561/src/DocBlock.php#L98-L117
from magento-lts.
I can create a PR in like 15 minutes to convert those few "real" tags that we lost (1 deprecated and a couple of "mixed" types) if wanted
from magento-lts.
Does OpenMage/Magento have a public phpDocumentor archive or why is that important to keep?
There is no public one, but maybe private?
With #3552 phpDocumentor looses some descriptions - for absolutly no reason.
I am also pretty sure we had a similar PR years ago, that was closed for same reason. (cant find it)
from magento-lts.
Closed with #3558
from magento-lts.
Related Issues (20)
- Fatal error: Uncaught Error: Call to a member function addData() on null HOT 2
- Deprecated functionality: preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated
- Deprecated functionality: strlen(): Passing null to parameter #1 ($string) of type string is deprecated
- Fatal error: Uncaught Error: Call to a member function setOnclick() on false HOT 2
- Deprecated functionality: nl2br(): Passing null to parameter #1 ($string) of type string is deprecated
- Deprecated functionality: htmlspecialchars(): Passing null to parameter #1 ($string) of type string is deprecated
- incorrect currency value HOT 4
- Use redis for session HOT 5
- Customer information missing after 19.5.3 -> 20.5.0 upgrade HOT 8
- Creating an order for a new registered customer - Required email address issue HOT 1
- Recaptcha HOT 2
- Payment and Shipping not selectable in backend (customer) order, but in frontend. HOT 1
- OpenMage (19.x and 20.x) appears incompatible with Amasty extensions
- onepage/billing.phtml required still displayed after removed. HOT 3
- Upgrading from 19.4.x to 20: recurring data is not saved
- Customers on online not showing HOT 3
- A recurring product is not calculated correctly in the cart HOT 3
- Long running queries presumably from layered navigation HOT 13
- PHP Error in frontend with improper request params HOT 2
- shardj/zf1-future patches all fail during composer install HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from magento-lts.