Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Smart Import

Hi,

how about **/index.php? , will be much faster than *.php and probably will find correct project.

But for example symfony projects haven’t index.php (even in vendor). They use web/app.php file.

-- 
Dawid Pakuła

From: Kaloyan Raev <kaloyan.r@xxxxxxxx>
Reply: PDT Developers <pdt-dev@xxxxxxxxxxx>
Date: 22 April 2016 at 17:37:07
To: PDT Developers <pdt-dev@xxxxxxxxxxx>
Subject:  Re: [pdt-dev] Smart Import

Hi, 


Great! This was in my TODO list for research, but I've never found the time 😊


I think having 'public/index.php' is also quite popular for PHP projects. 'index.php' in the project root might be also a good criterion.


Kaloyan




From: pdt-dev-bounces@xxxxxxxxxxx <pdt-dev-bounces@xxxxxxxxxxx> on behalf of Michal Niewrzal <michal.n@xxxxxxxx>
Sent: Friday, April 22, 2016 6:29 PM
To: PDT Developers
Subject: [pdt-dev] Smart Import
 

Hi All,


I'm thinking about implementing smart import support[1] for PHP projects. The main challenge is to define best strategy for project detection. First and easiest to detect is 'composer.json'. Framework gives option to scan whole project but I wonder if just searching for *.php files will not be to general. Let me know what do you think about it &#X1f60a


Thanks,

Michal 


[1] https://wiki.eclipse.org/E4/UI/Smart_Import

wiki.eclipse.org
Smarter import framework Purpose. Currently, when importing a project, users are facing the difficult choices of What project they're importing and How to import it.

_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/pdt-dev

Attachment: smime.p7s
Description: S/MIME cryptographic signature


Back to the top