* configured babel and jest to work with webpack
* added util function to camelize object entries
* added tests for apiconvert dashboard
* added enaming object key function
* finished refactoring of convertapi dashboard
* renamed camelize to transformObject
* renamed uuids to randomValues
* use random strings instead of hard coded values in test
* refactored dictionary.process and added tests
* refactored dashboard tests - test with json objects
* added first tests for apiConvert core
* made camelizeObjectkeys immutable
* added talismanrc to gitignore
* added all tests for apiConverts core
* added more dictionary tests
* finished refactoring apiConverts dictionary
* restructured objects in folders
* refactored apiConverts persistence
* refactored apiConvert pos
* refactored apiConvert privateAccess
* refactored apiConverts process
* refactored apiConverts report
* refactored apiConverts user
* refactored apiConverts values
* refactored apiConverts window
* linted all test files
* removed tests for privateAccess
* removed typos from prev implementation
* Add lock and unlock record to record access dialog box
* minima change
* support mobile
* minimal changes
* delete comment
* minimal changes
Co-authored-by: elsiosanchez <elsiosanche@gmail.com>
Co-authored-by: elsiosanchez <elsiossanches@gmail.com>
* Add API for get Record Access based on server
* support setRecordAcces
* Add mixin for view, this allows reuse code based on unique definition
* support record access
* Support Record Access in Mode Mobile
* minimal changes
Co-authored-by: elsiosanchez <elsiosanche@gmail.com>
* adding Point of Sale features
* Delete Ineccessary Getters
* minimal changes
* add list product Price and Order Line
* Add license
* minimal changes
* unify getters
* minimal changes
* minimal changes
Co-authored-by: Elsio Sanchez <elsiosanche@gmail.com>
* Fixes: #736
* get the currency code to be paid
* add the correct currency symbol in the amount field
Co-authored-by: Elsio Sanchez <elsiosanche@gmail.com>
* Add License to files inside project
This is recommended by GNU/gpl v3 according with it: https://www.gnu.org/licenses/gpl-3.0.html
```
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an “about box”.
You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <https://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <https://www.gnu.org/licenses/why-not-lgpl.html>.
```
* Remove space
