December 2019 – Page 11 – ソフトウェアエンジニアの技術ブログ：Software engineer tech blog

routeからcontrollerへのデータパス

getでcontrollerを呼ぶとき

Route::get('/post', 'PostsController@index');

public function index()
    {
        return "its working";
    }

ここで、routeからデータを渡したい
ブランケットで囲むとデータを引き継げる

Route::get('/post/{id}/', 'PostsController@index');

indexがfunction

public function index($id)
    {
        return "its working with" . $id;
    }

php artisan一覧

$ php artisan
Laravel Framework version 5.2.45

Usage:
command [options] [arguments]

Options:
-h, –help Display this help message
-q, –quiet Do not output any message
-V, –version Display this application version
–ansi Force ANSI output
–no-ansi Disable ANSI output
-n, –no-interaction Do not ask any interactive question
–env[=ENV] The environment the command should run under.
-v|vv|vvv, –verbose Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

Available commands:
clear-compiled Remove the compiled class file
down Put the application into maintenance mode
env Display the current framework environment
help Displays help for a command list Lists commands
migrate Run the database migrations
optimize Optimize the framework for better performance
serve Serve the application on the PHP development server
tinker Interact with your application
up Bring the application out of maintenance mode
app
app:name Set the application namespace
auth
auth:clear-resets Flush expired password reset tokens
cache
cache:clear Flush the application cache
cache:table Create a migration for the cache database table
config
config:cache Create a cache file for faster configuration loading
config:clear Remove the configuration cache file
db
db:seed Seed the database with records
event
event:generate Generate the missing events and listeners based on registration
key
key:generate Set the application key
make
make:auth Scaffold basic login and registration views and routes
make:console Create a new Artisan command
make:controller Create a new controller class
make:event Create a new event class
make:job Create a new job class
make:listener Create a new event listener class
make:middleware Create a new middleware class
make:migration Create a new migration file
make:model Create a new Eloquent model class
make:policy Create a new policy class
make:provider Create a new service provider class
make:request Create a new form request class
make:seeder Create a new seeder class
make:test Create a new test class
migrate
migrate:install Create the migration repository
migrate:refresh Reset and re-run all migrations
migrate:reset Rollback all database migrations
migrate:rollback Rollback the last database migration
migrate:status Show the status of each migration
queue
queue:failed List all of the failed queue jobs
queue:failed-table Create a migration for the failed queue jobs database table
queue:flush Flush all of the failed queue jobs
queue:forget Delete a failed queue job
queue:listen Listen to a given queue
queue:restart Restart queue worker daemons after their current job
queue:retry Retry a failed queue job
queue:table Create a migration for the queue jobs database table
queue:work Process the next job on a queue
route
route:cache Create a route cache file for faster route registration
route:clear Remove the route cache file
route:list List all registered routes
schedule
schedule:run Run the scheduled commands
session
session:table Create a migration for the session database table
vendor
vendor:publish Publish any publishable assets from vendor packages
view
view:clear Clear all compiled view files

make, migrate以外にもたくさんありますね。

Laravel Controller：–resource

filename:camelcase

namespace
-> namespace is wide scope does for variable basically allow

名前の集合を分割することで衝突の可能性を低減しつつ参照を容易にする概念

namespace App\Http\Controllers;

use
-> right to import that specific class or name space

use Illuminate\Foundation\Bus\DispatchesJobs;
use Illuminate\Routing\Controller as BaseController;
use Illuminate\Foundation\Validation\ValidatesRequests;
use Illuminate\Foundation\Auth\Access\AuthorizesRequests;
use Illuminate\Foundation\Auth\Access\AuthorizesResources;

artisanコマンドでの作成
$ php artisan make:controller PostsController

–resouceとすると、index(), function create(), store(Request $request), show($id), edit($id), update(Request $request, $id), destory($id)ができる
$ php artisan make:controller –resource PostsController

なるほど、method名がdeleteではなくdestroyってのは若干違和感を感じるが、こんなもんかしらね。

Laravel Route

基礎をやります。
パラメーターを渡す。

Route::get('/post/{id}/{name}', function($id, $name){
	return "this is post number " . $id . "," . $name;
});

asで引数を渡す。
パスが長い場合は書き換える

Route::get('/admin/posts/example', array('as'=>'admin.home', function(){
	$url = route('admin.home');
	return "this url is" . $url;

}));

php artisan route:listで表示

$ php artisan route:list
+——–+———-+———————+————+———+————+
| Domain | Method | URI | Name | Action | Middleware |
+——–+———-+———————+————+———+————+
| | GET|HEAD | / | | Closure | web |
| | GET|HEAD | about | | Closure | web |
| | GET|HEAD | admin/posts/example | admin.home | Closure | web |
| | GET|HEAD | post/{id}/{name} | | Closure | web |
+——–+———-+———————+————+———+————+

Github wikiの活用とブログとの切り分け

git hub wikiにプロジェクトのドキュメントを書いていく
記事単位のブログと違って、ページ単位だから、ノウハウ系のドキュメントはブログよりも管理しやすく、後から振り返る時も分かり易いかも。。

ブログはメモ、トラブルシューティング、自由日記みたいな感じだが、github wikiはどちらかというと、体系立てて、よりフォーマルな記述か。。

migration fileの修正・アップデート

public function up()
    {
        Schema::create('posts', function (Blueprint $table) {
            $table->bigIncrements('id');
            $table->timestamps();
        });
    }

カラムを追加して、もう一度migrateしたい時

public function up()
    {
        Schema::create('posts', function (Blueprint $table) {
            $table->bigIncrements('id');
            $table->string('title');
            $table->text('body');
            $table->timestamps();
        });
    }

一度migrateした後、修正してphp artisan migrateとしてもnothing to doとなる
$ php artisan migrate
Nothing to migrate.

そのような場合は、
$ php artisan migrate:reset
$ php artisan migrate

ローカルから空のgit repositoryへの最初のpush手順

githubでリポジトリを作った後、以下の手順でpushする
$ git init
$ git commit –allow-empty -m “first commit”
$ git remote add origin https://github.com/${username}/${repository}.git
$ git push -u origin master

空リポジトリをgit cloneして、そこからgit pushするわけではないのね。
道理で、git cloneした後に、${repository}/.git をmvコマンドでcurrentに移動するのはなんかおかしいな～と思ってた。。

Cannot read property ‘getState’ of undefined

main.js

import React from 'react'
import { render } from 'react-dom'
import { Provider } from 'react-redux'
import App from './components/App'

render(
	<Provider>
		<App />
	</Provider>,
	document.getElementById('app')
)

components/App.js

import React from 'react'

const App = () => (
	<div>
		Hello Redux!
	</div>
)

export default App

console.log
Provider.js:26 Uncaught TypeError: Cannot read property ‘getState’ of undefined

store定義していないから？？

Reduxを始める

まずReact.js&webpack&babelから
#################
$ npm init
$ npm install –save-dev webpack webpack-cli webpack-dev-server
$ npm install –save-dev @babel/core @babel/preset-env @babel/preset-react babel-loader
$ npm install –save-dev react react-dom
$ npm install –save-dev @babel/plugin-proposal-class-properties

.babelrc作成

{
	"plugins": [
		"@babel/plugin-proposal-class-properties"
	]
}

webpack.config.jsの作成
srcディレクトリの作成
#################

ここから、Reduxを使い始めたい。
公式に沿ってやっていく。(https://redux.js.org/introduction/getting-started）

npm i react-redux

$ npm install --save-dev react-redux
$ npm install --save-dev redux

basic example

import { createStore } from 'redux'

function counter(state = 0, action){
	swtich(action.type){
		case 'INCREMENT':
			return state + 1
		case 'DECREMENT':
			return state - 1
		default:
			return state
	}	
}

let store = createStore(counter)

store.subscribe(() => console.log(store.getState()))

store.dispatch({ type: 'INCREMENT' })
store.dispatch({ type: 'INCREMENT' })
store.dispatch({ type: 'INCREMENT' })

createStoreで状態遷移を管理？
全体の動きがよくわからんな。。

Month: December 2019

Laravel View