Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
lang-mini - npm Package Compare versions
Comparing version 0.0.12 to 0.0.13
@@ -9,3 +9,3 @@ { | ||
| "devDependencies": { | ||
| "fnl": "^0.0.11" | ||
| "fnl": "^0.0.13" | ||
| }, | ||
@@ -24,3 +24,3 @@ "comments": [ | ||
| }, | ||
| "version": "0.0.12" | ||
| "version": "0.0.13" | ||
| } |
229
roadmap.md
| Roadmap and progress notes. | ||
| Remove some functions | ||
| Check to see if they are used anywhere | ||
| Check to see if they are used anywhere | ||
| 07/06-2019 - Working on mfp - Multi-Function Polymorphism | ||
| Will have better understanding / modelling of parameters, including parameter names. | ||
| Will have better understanding / modelling of parameters, including parameter names. | ||
| Need to do more tests. | ||
| ``` | ||
| Need to do more tests. | ||
| ``` | ||
| 08/06/2019 - progress with mfp work. making a grammar definition system. | ||
| making a way so its possible to be much more explicit about what the function does to what data | ||
| providing the system with info on the function's API | ||
| this helps the function to be called programatically. | ||
| needed to fix a problem on a lower level concerning Evented_Class. | ||
| making a way so its possible to be much more explicit about what the function does to what data | ||
| providing the system with info on the function's API | ||
| this helps the function to be called programatically. | ||
| needed to fix a problem on a lower level concerning Evented_Class. | ||
@@ -29,30 +31,29 @@ When we have the grammar, and are told what object is the 'noun', we can deduce different ways that the function could be called | ||
| 0.0.11? | ||
| further usage of mfp throughout the system. | ||
| could make the larger apps more concise. | ||
| ``` | ||
| further usage of mfp throughout the system. | ||
| could make the larger apps more concise. | ||
| mfp and function grammar - have a .pure property for denoting a pure function. | ||
| definitely seems useful. | ||
| no side effects indicator. does not modify input. test suite could check it??? | ||
| mfp and function grammar - have a .pure property for denoting a pure function. | ||
| definitely seems useful. | ||
| no side effects indicator. does not modify input. test suite could check it??? | ||
| tf function - like tof, but returns abbreviated type names. | ||
| tc could use type constants - maybe would compress best. | ||
| Deep signatures | ||
| Examples. | ||
| Maybe even make tests of deep signatures? | ||
| A good regression test system would run the tests / order them sequentially so that the lower level things are tested first. | ||
| Identify the lowest levels where problems occurr. | ||
| tf function - like tof, but returns abbreviated type names. | ||
| tc could use type constants - maybe would compress best. | ||
| Deep signatures | ||
| Examples. | ||
| Maybe even make tests of deep signatures? | ||
| A good regression test system would run the tests / order them sequentially so that the lower level things are tested first. | ||
| Identify the lowest levels where problems occurr. | ||
| ``` | ||
| 0.0.11.3? Staged functions. | ||
| // Multiple stages of operation in a function. | ||
| // Needs to return result normally? | ||
| // An evented\_class for stage\_events? | ||
| // and also the function result? | ||
| 0.0.11.3? Staged functions. | ||
| // Multiple stages of operation in a function. | ||
| // Needs to return result normally? | ||
| // An evented_class for stage_events? | ||
| // and also the function result? | ||
| // The evented_class could still represent the stages without full obs functionality. | ||
| // as stages may be a building block of some observables? | ||
| // as stages may be a building block of some observables? | ||
@@ -62,18 +63,17 @@ Still unsure about how to do stages. | ||
| // Possibly it could be an observable of its own? | ||
| // don't want to get tangled in knots. | ||
| // don't want to get tangled in knots. | ||
| // a staged function creates a function. | ||
| // an Evented_Class with stage events may work best. | ||
| // an Evented_Class with stage events may work best. | ||
| // it would get more complacated making a whole new object / system. | ||
| // a stages(arr[...]) function would be a nice syntax | ||
| // observable may indeed be the best platform for 'stages'. | ||
| // and they could go inside a non-staged observable. | ||
| // observable may indeed be the best platform for 'stages'. | ||
| // and they could go inside a non-staged observable. | ||
| // or stages that are based on Evented_Class | ||
| // their own implementation. | ||
| // or stages that are based on Evented_Class | ||
| // their own implementation. | ||
| // or one observable could handle the stages of another. | ||
| // or one observable could handle the stages of another. | ||
@@ -83,49 +83,39 @@ // and stages would need an enclosing closure. | ||
| // stages would really help in some ways. | ||
| // keeping the stages separate | ||
| // monitoring them | ||
| // keeping the stages separate | ||
| // monitoring them | ||
| // maybe leave the stages for the moment, consider it a bit more | ||
| // though stages would indeed be a very useful syntax. | ||
| // though stages would indeed be a very useful syntax. | ||
| // maybe write the inner parts as different stages anyway, leaving out new platform parts for the moment. | ||
| // defining stages with their param types would help understand program flow too. | ||
| // defining stages with their param types would help understand program flow too. | ||
| // [stage_events] | ||
| 0.0.11.5? Constraints? | ||
| Would be nice with a functional and extendable mechanism. | ||
| Lower priority for the moment. | ||
| maybe make constrining functions. | ||
| Would be nice with a functional and extendable mechanism. | ||
| Lower priority for the moment. | ||
| maybe make constrining functions. | ||
| 0.0.12? - Application Domain Grammars: | ||
| 10/06/2019 Getting grammar done already | ||
| 02/07/2019 - Been working on / stuck on stages for a while. Solved it now. | ||
| Now getting back to grammars. | ||
| Grammars within the system. Grammars within a specific function context. | ||
| Want some general purpose grammar processing? | ||
| And / or for solving some specific grammar tasks to do with parameter identification. | ||
| 10/06/2019 Getting grammar done already | ||
| 02/07/2019 - Been working on / stuck on stages for a while. Solved it now. | ||
| Now getting back to grammars. | ||
| Grammars within the system. Grammars within a specific function context. | ||
| Want some general purpose grammar processing? | ||
| And / or for solving some specific grammar tasks to do with parameter identification. | ||
| Being able to apply a grammar object to things would help. | ||
| A grammar makes sense as an object. | ||
| Not as functions? | ||
| ``` | ||
| Being able to apply a grammar object to things would help. | ||
| A grammar makes sense as an object. | ||
| Not as functions? | ||
| Encapsulating a grammar in a function / class makes sense. | ||
| Encapsulating a grammar in a function / class makes sense. | ||
| ``` | ||
| Getting grammar done, now that stages is mostly done, would make sense. | ||
| Want to be able to interpret objects in specific ways. | ||
| 16/07/2019 - Have got the Grammar class. | ||
| 16/07/2019 - Have got the Grammar class. | ||
| ??? Ideally get down to 3KB compressed. | ||
@@ -135,12 +125,13 @@ | ||
| What is clear: | ||
| Should be swappable - different grammar systems possible | ||
| Not clear how to do that yet | ||
| Grammar API | ||
| Worth making that to define what the grammar needs to do, what it will get as input. | ||
| Can fit in one file. | ||
| Should be swappable - different grammar systems possible | ||
| Not clear how to do that yet | ||
| Grammar API | ||
| Worth making that to define what the grammar needs to do, what it will get as input. | ||
| Can fit in one file. | ||
| Lots of different grammar instances could be created. Various functions will be defined with local grammars. | ||
| Functions could be written so that they reference part of a more comprehensive grammar. | ||
| ``` | ||
| Lots of different grammar instances could be created. Various functions will be defined with local grammars. | ||
| Functions could be written so that they reference part of a more comprehensive grammar. | ||
| Such grammars would also have uses in driving / dynamically creating GUIs based on the data structures. | ||
| Such grammars would also have uses in driving / dynamically creating GUIs based on the data structures. | ||
@@ -150,64 +141,66 @@ | ||
| Out-of-the-box mini grammar: | ||
| may be worth defining a grammar parsing / checking API. | ||
| Out-of-the-box mini grammar: | ||
| may be worth defining a grammar parsing / checking API. | ||
| // give the grammar object definitions | ||
| // it does some preparation work | ||
| // give the grammar POJOS | ||
| // can tell which object definitions are matched. | ||
| uses strings. works well so far. | ||
| // give the grammar object definitions | ||
| // it does some preparation work | ||
| // give the grammar POJOS | ||
| // can tell which object definitions are matched. | ||
| uses strings. works well so far. | ||
| Object arrangements? Templates? | ||
| Going for 'grammar'. Maybe we could talk of templates later. | ||
| object-arrangements module? | ||
| so they can be defined and found? | ||
| Making use of object schemas within these grammars? | ||
| // https://json-schema.org/ | ||
| Object arrangements? Templates? | ||
| Going for 'grammar'. Maybe we could talk of templates later. | ||
| 10/06/2019 - Essentially done for the moment / not being implemented soon. | ||
| Maybe JSON schema could do the job? | ||
| Would need to use JSON Schema to see which objects within the grammar match the structure of the parameters to a function call. | ||
| not using it now, too large and complex. | ||
| object-arrangements module? | ||
| so they can be defined and found? | ||
| Making use of object schemas within these grammars? | ||
| // https://json-schema.org/ | ||
| ``` | ||
| Getting more formally into grammar, as in using an existing standard, while keeping a small codebase, will be very useful. | ||
| 10/06/2019 - Essentially done for the moment / not being implemented soon. | ||
| Maybe JSON schema could do the job? | ||
| Would need to use JSON Schema to see which objects within the grammar match the structure of the parameters to a function call. | ||
| not using it now, too large and complex. | ||
| JSON schema standard is possibly too long. | ||
| Make it available as a grammar plugin? | ||
| Estensible grammars would definitely help. | ||
| Would help me make an initial grammar version that does not have to be perfect. | ||
| ``` | ||
| Getting more formally into grammar, as in using an existing standard, while keeping a small codebase, will be very useful. | ||
| https://github.com/epoberezkin/ajv | ||
| JSON schema standard is possibly too long. | ||
| Make it available as a grammar plugin? | ||
| Estensible grammars would definitely help. | ||
| Would help me make an initial grammar version that does not have to be perfect. | ||
| Full JSON schema is a bit large. | ||
| https://github.com/epoberezkin/ajv | ||
| Minimal JSON schema? | ||
| Minimal Object Schema? | ||
| Full JSON schema is a bit large. | ||
| https://www.npmjs.com/package/ajv | ||
| https://bundlephobia.com/result?p=ajv@6.10.0 | ||
| Very useful results there | ||
| Minimal JSON schema? | ||
| Minimal Object Schema? | ||
| Can use existing object validators | ||
| Will mean we can validate objects (all the params as an array) against the objects defined in the grammar. | ||
| https://www.npmjs.com/package/ajv | ||
| https://bundlephobia.com/result?p=ajv@6.10.0 | ||
| Very useful results there | ||
| JSON schema looks like a decent standard to use, especially if existing and small implementations will do the job well. | ||
| Even adding to lang-mini? | ||
| Makes sense if it's small and compresses well. | ||
| Can use existing object validators | ||
| Will mean we can validate objects (all the params as an array) against the objects defined in the grammar. | ||
| However, shorthand string definitions seem like the best way for the moment. | ||
| Own custom mini-validator | ||
| Worth considering extensibility and API for that. | ||
| JSON schema looks like a decent standard to use, especially if existing and small implementations will do the job well. | ||
| Even adding to lang-mini? | ||
| Makes sense if it's small and compresses well. | ||
| https://github.com/tdegrunt/jsonschema | ||
| However, shorthand string definitions seem like the best way for the moment. | ||
| Own custom mini-validator | ||
| Worth considering extensibility and API for that. | ||
| Deeper level signatures may do the job. | ||
| https://github.com/tdegrunt/jsonschema | ||
| Deeper level signatures may do the job. | ||
| ``` | ||
| 0.0.13? w word item signature type | ||
| can separate multiple string params when there is a space. | ||
| can separate multiple string params when there is a space. | ||
| ? Tests and examples built together. | ||
| Building up larger examples? | ||
| Documentation? | ||
| Building up larger examples? | ||
| Documentation? |
Sorry, the diff of this file is too big to display
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
No README
QualityPackage does not have a README. This may indicate a failed publish or a low quality package.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.5%
331856
- Number of package files
- increased by6.25%
17
- Lines of code
- increased by0.31%
8751
- Number of medium quality alerts
- decreased by-50%
1
- Number of lines in readme file
- increased byInfinity%
67
No dependency changes