velliz / pukoframework Goto Github PK

Originally, expired is defined as constant variable in Auth Abstract Class

const EXPIRED_ON_CLOSE = null;
const EXPIRED_1_HOUR = 3600;
const EXPIRED_1_DAY = 86400;
const EXPIRED_1_WEEK = 604800;
const EXPIRED_1_MONTH = 2592000;

That constant used with this technique:

Session::Get(Tamu::Instance())->Login($param['username'], $param['password'], Auth::EXPIRED_1_DAY);
Cookies::Get(Tamu::Instance())->Login($param['username'], $param['password'], Auth::EXPIRED_1_DAY);
Bearer::Get(Tamu::Instance())->Login($param['username'], $param['password'], Auth::EXPIRED_1_DAY);

Later, variable expired introduced on config/encryption.php on line "expired = 30" but seems the implementation still not complete across all Auth classes.

Glossary:

Q: expired is set in 30 by default as? hour? day? minute? seconds?
A: Wee will make it as minute.

In puko, all error trowed as exceptions. Will great if puko can have another like:

• Exception (general) - 403
• Value Exception
• Render Exception
• Controller Exception
• Model Exception

And also:

• Service un-catch error - (500 + json error page)
• View un-catch error - (500 + html error page)

Until now, pukoframework don't have transactional feature, so i decided to add this function in next release into the PDA section on this framework.

Usage demonstration in my head so far,,, archived in 3 different way:

• DBI ORM Style

$transaction = DBI::Transactional('primary');

$x = new obj();
...
$x->save($transaction);
...
$y->modify($transaction);
...

$transaction->commit();
$transaction->cancel();

• DBI Original

$pk = 'id';
$data = [...];
$id = [...];

DBI::Prepare('users', 'primary')->Save($data, $pk, $transaction);
DBI::Prepare('users', 'primary')->Update($id, $data, $transaction);
DBI::Prepare('users', 'primary')->Delete($id, $transaction);

$transaction->commit();
//or
$transaction->cancel();

• DBI Function Component (Idea comes from doctrine and laravel implementation)

$result = DBI::Transactional('primary', function($DBI) {

   $x = new obj();
   ...
   $x->save($DBI);
   ...
   $y->modify($DBI);
   ...

});

A lot of works happens in DBI class. Witch i must move out the $dbi instance out. So the object is being reusable in the transaction lifecycle.

Let's see if there was a progress in here.

Most requested feature.
Master HTML layout can assigned via:
@template master url_to_file

Outer tag {!Name} also replacing tag {!Name} in loop section.

{!Name}

<!--{!Members}-->
{!Name}
<!--{/Members}-->

So, for now we must have unique value tag to patch this issue.

DBI class.

DBI->Prepare($sql)->GetData($user, $pass);

has potential SQL injection with key

'=''or'
'

and many SQL keywords.
this must fixed ASAP!

Apakah ada dokumentasi penggunaan framework puko?

Until version 1.0.3 puko framework is throwing error if view file is not found or empty.
Enhancement:

1. Allow empty HTML
2. Allow if template master not found

Bisakah saya berhkontribusi? jika iya, bagian mana yang perlu penanganan. Sepertinya framework anda bagus. Namun lebih bagus jika dikelola lebih dari satu orang. Supaya lebih berkembang