Comments (11)
Honestly I think that's just lazy. ⛵
See what others think though.
from framework.
I guess if your only writing a single package, i was just thinking it would be nice not to have to enter the same information again and again.
from framework.
Copy paste! :)
from framework.
I agree with @jasonlewis that it's kind of very low priority, if at all.
Having said that, it's kind of lazy, but aren't we all? :D
If we weren't, there wouldn't be code completion in editors, etc... ;)
I haven't dived into artisan commands yet, but couldn't this functionality be a separate package, if not in the base distribution? Maybe @iccle could implement that?
from framework.
I remember seeing an issue about adding a config file with default values for name and email - that would probably be an easier way and would still fulfill your need, right?
from framework.
Hmmm, can't imagine this being a priority.
from framework.
I didnt expect it to be priorty, and dont think its particularly lazy i prefer to enter data once and re-use it instead of re-entering it.
My thinking was how often do i change my name or email? Never. So it would be nice for workbench to remember me saving me from pesky typos as i repeatedly enter my information. This could be extended to store your favorite licence choice for your composer.json.
Other artisan commands may benefit from some sort of persistant/global config, eg it would be nice to set the default namespace used for controllers once (for my project or whatever) then have commands that use --namespace read it in if no namespace is specified on the command line.
Im still feeling my way around the new code, may look into making something like this once i find my feet.
from framework.
I think this is a great idea. I think it just needs to be a simple config file. Artisan would first check if the config file exists and use those settings unless overridden in the command. If no config file or not in the command then prompt for it.
As iccle mentions, other commands could benefit from this. For example migrate:make, you could change the path from app/migrations and not have to retype it every time. New packages could install config defaults for commands as well. For example with laravel-bob bundle you could always have bob controller use --blade and --restful.
Definitely not high priority, however Its the little things that make laravel so great.
from framework.
+1 on making it a config entry.
from framework.
Since your typing / config files for name and emails are just populating stubs, could Artisan not be made to check a custom stubs directory outside of all projects for all of its commands. You could then also configure, for instance, phpunit.xml not to have colors set to true (as that makes it all screwy in Windows), have the service provider and controller stubs start off as PSR-2, custom travis config etc.?
from framework.
This is implemented via the new workbench
configuration file.
from framework.
Related Issues (20)
- Nova on Laravel 11 crashes with 'Route [login] not defined' HOT 2
- Custom route binding for enums doesn't work anymore HOT 1
- Laravel 11 SQLite Migration Failure: Error Dropping Columns with RefreshDatabase in PHPUnit Tests HOT 2
- Redis stores number as string HOT 3
- WithoutRelations Attribute is not respected by SerializesModels, when the attribute is on a parent class HOT 1
- Eloquent Relation Bug
- Event Auto Discovery not working with vendor package HOT 3
- Exceptions render is not being called for some Laravel and Symfony exceptions HOT 3
- Passport issue in laravel 11 HOT 4
- Issues with Testing and Routing After Upgrading to Laravel 11.0 HOT 1
- Unexpected newline behavior in blade template with echo followed by verbatim HOT 4
- Null Parameter Deprecation Notices HOT 1
- `Bus::dispatch()` cannot be used to queue closures HOT 1
- Throttle middleware with unnamed limiters behave weirdly HOT 3
- Escaped PHP code rendered instead of section contents in Blade template HOT 2
- Enable broadcasting after upgrade Laravel from 10.x to 11.x HOT 1
- Default connection is being changed unreliably in testing HOT 1
- The `Paginator` interface does not implement `through` method HOT 1
- Route file is broken when use a method to define return
- Maria DB before 10.5.2 rename nullable column fails HOT 5
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 framework.