The create and build steps will create the form field templates, and then build them into a Javascript library file for you to include into your project. You can use the standard field templates (and then apply your own CSS styles for customisation), or if you prefer you can modify the templates themselves to create a highly customised form output.
At this stage, if you're happy with your project setup, you're now able to run the bm forms create command. :
| Column |
|---|
|
| Code Block |
|---|
| bm forms create |
|
This will create the library source by reading your forms definition and using the templates specified by the plugin you selected in the init step.This command will build the library automatically, however you can prevent this command from building so that you're able to edit the source files/templates first, should you require further customisation - we've included the
If you would like to modify the standard templates, you can do so by using the create command with the --no-build build flag for this purpose.
| Div |
|---|
When running the command, you have the following two options:
Will create and build your library source
| Code Block |
|---|
|
bm forms create |
Will create your library without building or compiling your code
| Code Block |
|---|
. This will create the templates, but not perform the final build step:
| Column |
|---|
|
| Code Block |
|---|
| bm forms create --no-build |
|
Now that Once you've built your library sourcerun this command, you can look at tweaking your templates to customise your outputthen modify the template files.
| Info |
|---|
We recommend running bm forms create before editing the templates so you can see what a default form will look like. |
my-forms/templates contains templates used by the transforms in the plugin. You can modify them to include any html/javascript you want, and commit them to your own version control for future reusability.
For more information on editing the templates, see the template documentation.
If you have modified your source files after this process, you will need to run the build command again. This will build out the library from the source folder:
| Info |
|---|
| It is important to note that bm forms create will overwrite anything in the sourcePath folder. If you have modified anything in the sourcePath folder, running bm forms create will remove it. |
If you've followed through these steps, you will You should now have my-forms/src and my-forms/dist folders on your local machine:
| Column |
|---|
|
| Panel |
|---|
| bgColor | lightblue |
|---|
| borderStyle | solid |
|---|
| |--my-project/
| |--.git/
| |--node_modules/
| |--my-forms/
| | |--dist
| | |--src
| | |--templates/
| |--.blinkmrc.json
| |--package.json
|
|
Depending on the framework plugin used, the
/ folder will contain your form components. Will contain the Javascript libraries ready for integration into your app, as well as an index.html example file that shows you how to include the libraries and dependencies.
Will contain the individual Javascript and components for your project. This does not need to be included in your project for deployment.
Managing Plugins