issues
search
Pomax
/
use-models-for-data
Work with your data through well-defined, always-consistent models, instead of rando plain JS objects
4
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add a `form` helper to the __meta object to guide form generation
#18
Pomax
opened
2 years ago
1
Async create
#17
Pomax
closed
2 years ago
0
improved migration handling
#16
Pomax
closed
2 years ago
0
make loadSchema async
#15
Pomax
opened
2 years ago
0
make saveSchema async
#14
Pomax
opened
2 years ago
0
rewrite diff tests
#13
Pomax
opened
2 years ago
0
add form tests
#12
Pomax
opened
2 years ago
0
add migration tests
#11
Pomax
opened
2 years ago
0
Create dedicated error objects for catch-testing
#10
Pomax
closed
2 years ago
1
Make sure everything works without model __meta
#9
Pomax
closed
2 years ago
1
Figure out how to make the SVGs look good
#8
Pomax
opened
2 years ago
1
Add an "autosave = true" ability to models
#7
Pomax
opened
2 years ago
0
Make model save/load async by default
#6
Pomax
closed
2 years ago
3
Add a .rollback() to models, to reset a model to its last known, good, pre-valid-updates state?
#5
Pomax
opened
2 years ago
0
Add a "one or more" field type
#4
Pomax
closed
2 years ago
1
split off "store agnostic" model tests to `models.test.js`
#3
Pomax
closed
2 years ago
1
add Fields.choice(...) for untyped choice lists
#2
Pomax
closed
2 years ago
1
come up with a way to say "read-only" in addition to "configurable"
#1
Pomax
opened
3 years ago
0