Ryan Glover

New version needs docs + examples

6

Was surprised to see a new release of this. I love this package but the changes to the API in the new version are fairly confusing and the documentation is...

The function should receive the entirety of the input from the client, returning a validation rule. The idea being to make it so that a developer can conditionally apply rules...

This has come to mind a few times. Goal would be to offer a simple API that developers could use to encrypt data before storing and when retrieving. Something like...

Gotchas

1

I think it'd be helpful/novel to document gotchas in the framework. Basically, things that are a "wtf?" in the code that are done to get around some gotcha in JavaScript...

Consider adding a way to write logs to a database

2

This is a maybe. There are a lot of situations where having logs from STDOUT/STDERR queryable from a DB would be extremely helpful. In Joystick, it wouldn't be terribly difficult...

Just a thought while writing a query for some data that could be globally cached. It's a bit risky due to memory constraints, but it'd be nice to be able...

Add a way to copy fetched data to state

1

This comes up fairly often. There are situations with forms where data fetched from the server needs to be popped on to state. It'd be helpful to have a flag...

It'd be nice to have some short-hand aliases baked in to Joystick for DOM selection. For example... ```javascript // Old document.querySelector('.blah'); document.querySelectorAll('.blah'); // Short-hand $.qs('.blah'); $.qsa('.blah'); ``` No change in...

Not 100% sure of the API for this yet, but something like this would be helpful: ```javascript form('signup', { classes: { labels: 'mod-label', inputs: 'mod-input', }, rows: [{ fields: [...

Implement a custom uploader middleware

1

Multer works for now, but the API isn't great and I think there's a better approach. Maintenance of the library is also ambiguous, so I'd rather this be maintained under...