You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should move the logic that prepares the arguments and calls autotrace and fontcustom to lib folders: (e.g. lib/autotrace.js and lib/fontcustom.js or something like that), then we can test those pieces more easily, use them in the webapp part, and provide a library that can be required in by other libraries.
The following is a list of things that I think will accomplish the above:
lib folder with autotrace and fontcustom specific code
index.js will be a Fontastic object that uses the files from the lib folder
path configuration should be passed to Fontastic and options can be passed to autotrace and fontcustom specific methods.
workflow should be handled in Fontastic methods.
routes handle transforming req/res specific properties to arguments passed to Fontastic methods.
The text was updated successfully, but these errors were encountered:
I think we should move the logic that prepares the arguments and calls
autotrace
andfontcustom
to lib folders: (e.g.lib/autotrace.js
andlib/fontcustom.js
or something like that), then we can test those pieces more easily, use them in the webapp part, and provide a library that can be required in by other libraries.The following is a list of things that I think will accomplish the above:
lib
folder withautotrace
andfontcustom
specific codeindex.js
will be aFontastic
object that uses the files from thelib
folderFontastic
and options can be passed toautotrace
andfontcustom
specific methods.Fontastic
methods.req/res
specific properties to arguments passed toFontastic
methods.The text was updated successfully, but these errors were encountered: