Use webpack build in CI process to ensure the source code build is ok

$this->input('blah', true)

Trongate 2
post('blah', true)

The demo was from our version 0.0.1 and has been a lot of the changes, specially the CSS Selector dropdown trigger is CTRL + ALT + CMD/ WIN/ SUPER + /

We also got sub module creation support and prevent bad module name

• General module creation demo gif

• Sub module creation demo gif

• Nitro demo gif

• Code Snippets

Just tested, if the user names its module with xxxxxx_module, then it would break if the user does not change the trigger phase in the config file, this could not be called a bug, but it is potentially there.

It would be an exciting idea to bring more popular front-end framework into the trongate vscode extension.

• https://picturepan2.github.io/spectre/index.html

• https://neu.useaxentix.com/

• https://useaxentix.com/ see PR: #31 --> Currently working on

• https://blueprintcss.dev/

• W3C

This potential issue has been bothered us for a while #10

When the user names its module with a module trigger phase and then will get a blank page, and it is super hard to debug.
If the user changes the module trigger phrase, then, our dynamically generated module would crash as we previously hard coded the module trigger phrase to _module.

Now, we fixed this issue in #23.

The extension will dynamically read the config file and extract the MODULE_ASSETS_TRIGGER and if the user names its module which contains the trigger phrase, the extension will terminate the process and let the user know what happened.

Besides, if the user changes the module trigger phrase in the config file, the view file will not fail as we dynamically links up the module trigger phrase.

Excellent extension.

For those wondering how to set a new file to php by default.

Files > Preferences > Settings
Files: Default Language

Enter php in the box.

Currently the selected CSS framework is shown in the bottom status bar, but it is not clickable, the way to trigger CSS framework selection is to use command, which is not user friendly (especially for beginners).

1. the function body created by tgm has a little bit of issue with format:

function index () {

}

There is an unwanted space in between function name and parenthesis

2. when use tg:submit, the cursor should be positioned at validation function

Thanks David for the suggestion.

Code Side:

• Give user a notice once they change the front-end framework - a pop up message and a status bar message will show up

• Fix the key binding on Mac ctrl + cmd + alt + n and ctrl + cmd + alt + p not working - replace with other keys (Mac only)

• Add essential dependencies and remove the redundant dependencies from package.json - reduce the extension size

• Add more commonly used snippets in terms of PHP @DaFa66 @jakecastelli

• Write essential comments in case collaboration or future maintains

• Code Refactor

• Figure out how to make it compatible even with lower version of VSCode as mentioned here #2

• A tinny new feature that can persist user's Nitro Framework selection

File Structure Side:

• Structure the front-end framework snippets into a separate folder - such as snippets/front-end-framework/milligram.json - in order to separate trongate php snippets and front-end frameworks

• Remove the junk folder as it is not needed

README Side:

• Add explanation for Nitro usage

• Demo for Nitro - suggestion: if you could figure out the way to show your key pressed on the screen that would be helpful @DaFa66

• Add to snippet table if any new snippet gets added

Testing Side:

• Fully test it on Windows @DaFa66

• Fully test it on MacOS @jakecastelli

• Fully test it on Linux @jakecastelli

Code Snippet for api.json --> API EXPLORER

Packing

• Pack it with webpack - reduce the extension size massively @jakecastelli

Heavy Testing

• Window @DaFa66

• MacOS @jakecastelli

• Ubuntu @jakecastelli

• Gif, ReadMe @DaFa66 @jakecastelli

I just came up with few new thoughts, and maybe worth to keep tracking them here in case I forget later.

• Create a new Trongate Module only the parent folder is modules - this would prevent the user to create a new module under a wrong dir

• Discuss about how to trigger the front-end framework snippets, at the moment is tg:{framework name initial}:{object you want to create} - this might not be ideal as all the snippet suggestions would pop up once you type tg:

• Add more Trongate related snippets to tg.json

• Refactor the code before publishing to the marketplace

When trying to install this extension i get this error message.
I'm on a Mac btw if that makes a difference.

"Unable to install 'jc-sf.trongate' extension because it is not compatible with the current version of VS Code (version 1.48.2)."

Update Summary:

• IMPORTANT the new release will be able to support super module creation #23

• The v1.0.2 release will allow the user to name the view file rather than hardcoded module name + _view

• Fixed a couple of typos which was found in v1.0.1 such as -> #20, thanks to @monxian

• Improved cursor position after create a new module

Testing:

• Windows @DaFa66

• MacOS @jakecastelli

• Linux @jakecastelli

Add License

• MIT License

README:

• Update README @DaFa66 @jakecastelli

When create a new module, the extension should first determine if it is a general module or a super module.

The boilerplate code for super module is different from general module.

Resource interpreted as Stylesheet but transferred with MIME type application/x-empty: xxx.

This is because the generated css file is default empty. The easiest way to get around is to add a comment line inside css file.

• Edit README - mention the changes - #29

• Add license - MIT - #29

• Change the version number - #29

`<?php
class Test extends Trongate {

function index () {
    $data['view_module'] = 'test';
    $this->view('test_view', $data);
    /* Uncomment the lines below, 
     * Change the template method name, 
     * Remove lines above, if you want to load to the template
     */
    //$data['view_module'] = 'test';
    //$ data['view_file] = 'test_view';
    //$this->template('template method here', $data);
}  

}`

In the commented out line the view file one. $data has a space $ data and the brackets need a closing apostrophe.

As Trongate Framework itself has got some update overtime such as 👉 #34
We need to address all the update / breaking changes in trongate-vscode extension, also consider bring in Trongate CSS

• #32
• #34
• #36
• Move changelog from README to CHANGELOG
• In README we prior Trongate over BS4
• #37
• #40

The new Trongate Module part still need to be refactored - simply three reasons:

1. Make the code more readable to the future contributors

2. Decouple the modules and functions as more features can be expanded upon the existing code base

3. Fix type annotation errors and interfaces