Deploy jsgenerator-core on Maven / Gradle as soon as possible
Opened this issue · 1 comments
In order to achieve this goal, the following tasks should be done. This list will be updated. This issue #12 explained what to do in details.
-
Verify that everything works fine
-
Now, We don't need to add these criterias, we'll only render as it is but let's keep this idea
First, we ask the user if the html input contains only HTML 5 tags or not (there are some custom tags) then we'll raise exception if custom tags are used or not. To be more precise, we'll throw exception if the user informed us that there are only HTML 5 tags but custom tags are also present. On the other hand, we do nothing if the user informed us that there are custom tags. A way to implement that is to have a boolean flag, true if we only have HTML5 tags, false if we have custom tags. #147 -
Secondly, we will ask if the user wants to use LET or VAR or CONST
-
Thirdly, the user has choice to copy and paste html code or submit file as input then get a Js code or file as output. It will be also possible to get both Js code or file if the user wants to do so. I mean, if the user choose the Js code as output, it would be possible to get also the file. If the user choose the Js file as output, it would be possible to get also the content. ( Client Implementation)
-
It's very important to handle the files very well. Should we let the user to choose where the html file is and choose where to save the js file or invite the user to use the predefined folders htmlInputFolder and jsOutputFolder ? ( Client Implementation)
-
Logic errors to correct or features to implement
-
-
-
Create a module in order to use core as a dependency
-
Deploy on Maven Repository https://mvnrepository.com/
-
Test that Maven/Gradle project has access to the dependency and is able to use every feature