dphelper 1.3.0 → 1.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.github/README.md +7 -5
- package/README.md +7 -5
- package/index.d.ts +1 -0
- package/index.js +1 -1
- package/package.json +6 -7
- package/types/_cookie.d.ts +50 -0
- package/57.ad9b3a5a60125c65d2b4.hot-update.js +0 -1
- package/index.ad9b3a5a60125c65d2b4.hot-update.json +0 -1
package/.github/README.md
CHANGED
|
@@ -26,7 +26,7 @@ You can use with html, react, vue or any other frontend / library.
|
|
|
26
26
|
## What you need to know about "no-refresh/reload" 🧐
|
|
27
27
|
|
|
28
28
|
dpHelper is designed to work primaly with website, application and portals that use "AJAX / XMLHttpRequest" technology like PWA, SPA, Angular, React, JQuery etc.
|
|
29
|
-
What mean?... So, modern browser and modern application use "NO REFRESH" behavior and these render only the part of browser needs changes instead re-render o refresh the entire page. Refresh o reload the entire page cause the lose of entire "states" ... my suggestion is to redesign/rewamp
|
|
29
|
+
What mean?... So, modern browser and modern application use "NO REFRESH" behavior and these render only the part of browser needs changes instead re-render o refresh the entire page. Refresh o reload the entire page cause the lose of entire "states" ... my suggestion is to redesign/rewamp your code using a technology more robust and faster. So, if you want to use dpHelper as state / store manager you can use only store function in a non Ajax engine. Feel free to contact me in case you need support or more information.
|
|
30
30
|
|
|
31
31
|
Here some links for you:
|
|
32
32
|
|
|
@@ -36,7 +36,7 @@ Here some links for you:
|
|
|
36
36
|
|
|
37
37
|
[XMLHttpRequest](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest)
|
|
38
38
|
|
|
39
|
-
|
|
39
|
+
You are not a tech guy, nerd or geek? ... no worries. Fix it... go to hiring one 🤭
|
|
40
40
|
|
|
41
41
|
## The Best Way To Use State and Store 💥
|
|
42
42
|
|
|
@@ -72,7 +72,7 @@ If you want to run a funtion everytime a state change you can use:
|
|
|
72
72
|
observer("test", ()=> alert( "Test Changes to: " + state.test ) )
|
|
73
73
|
```
|
|
74
74
|
|
|
75
|
-
You can use it everywere. Works like "useState" in react but with more flexibility
|
|
75
|
+
You can use it everywere. Works like "useState" in react but with more flexibility ( use one observer each state! )
|
|
76
76
|
|
|
77
77
|
## State vs Store 🎅
|
|
78
78
|
|
|
@@ -132,9 +132,11 @@ note: you don't need to use npm install in this case or you get an error
|
|
|
132
132
|
|
|
133
133
|
## How to use it
|
|
134
134
|
|
|
135
|
-
type 'dphelper'
|
|
135
|
+
type 'dphelper' in the console of your browser to have a look about all available & tools that you can use!
|
|
136
136
|
|
|
137
|
-
You can call these from everywhere without import (just one
|
|
137
|
+
You can call these from everywhere without import (just one time in main / root page)
|
|
138
|
+
|
|
139
|
+
---
|
|
138
140
|
|
|
139
141
|
## Browser Extension (Chrome/Edge) ♥️
|
|
140
142
|
|
package/README.md
CHANGED
|
@@ -26,7 +26,7 @@ You can use with html, react, vue or any other frontend / library.
|
|
|
26
26
|
## What you need to know about "no-refresh/reload" 🧐
|
|
27
27
|
|
|
28
28
|
dpHelper is designed to work primaly with website, application and portals that use "AJAX / XMLHttpRequest" technology like PWA, SPA, Angular, React, JQuery etc.
|
|
29
|
-
What mean?... So, modern browser and modern application use "NO REFRESH" behavior and these render only the part of browser needs changes instead re-render o refresh the entire page. Refresh o reload the entire page cause the lose of entire "states" ... my suggestion is to redesign/rewamp
|
|
29
|
+
What mean?... So, modern browser and modern application use "NO REFRESH" behavior and these render only the part of browser needs changes instead re-render o refresh the entire page. Refresh o reload the entire page cause the lose of entire "states" ... my suggestion is to redesign/rewamp your code using a technology more robust and faster. So, if you want to use dpHelper as state / store manager you can use only store function in a non Ajax engine. Feel free to contact me in case you need support or more information.
|
|
30
30
|
|
|
31
31
|
Here some links for you:
|
|
32
32
|
|
|
@@ -36,7 +36,7 @@ Here some links for you:
|
|
|
36
36
|
|
|
37
37
|
[XMLHttpRequest](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest)
|
|
38
38
|
|
|
39
|
-
|
|
39
|
+
You are not a tech guy, nerd or geek? ... no worries. Fix it... go to hiring one 🤭
|
|
40
40
|
|
|
41
41
|
## The Best Way To Use State and Store 💥
|
|
42
42
|
|
|
@@ -72,7 +72,7 @@ If you want to run a funtion everytime a state change you can use:
|
|
|
72
72
|
observer("test", ()=> alert( "Test Changes to: " + state.test ) )
|
|
73
73
|
```
|
|
74
74
|
|
|
75
|
-
You can use it everywere. Works like "useState" in react but with more flexibility
|
|
75
|
+
You can use it everywere. Works like "useState" in react but with more flexibility ( use one observer each state! )
|
|
76
76
|
|
|
77
77
|
## State vs Store 🎅
|
|
78
78
|
|
|
@@ -132,9 +132,11 @@ note: you don't need to use npm install in this case or you get an error
|
|
|
132
132
|
|
|
133
133
|
## How to use it
|
|
134
134
|
|
|
135
|
-
type 'dphelper'
|
|
135
|
+
type 'dphelper' in the console of your browser to have a look about all available & tools that you can use!
|
|
136
136
|
|
|
137
|
-
You can call these from everywhere without import (just one
|
|
137
|
+
You can call these from everywhere without import (just one time in main / root page)
|
|
138
|
+
|
|
139
|
+
---
|
|
138
140
|
|
|
139
141
|
## Browser Extension (Chrome/Edge) ♥️
|
|
140
142
|
|
package/index.d.ts
CHANGED