TheoryOfNekomata 8875c63f48 | 3 years ago | |
---|---|---|
cypress | 3 years ago | |
src | 3 years ago | |
.gitignore | 3 years ago | |
.npmignore | 3 years ago | |
.prettierrc | 3 years ago | |
LICENSE | 3 years ago | |
README.md | 3 years ago | |
cypress.json | 3 years ago | |
jest.config.js | 3 years ago | |
package.json | 3 years ago | |
publish.sh | 3 years ago | |
tsconfig.json | 3 years ago | |
yarn.lock | 3 years ago |
(read “form extra”)
Extract form values through the DOM.
Forms are used to package related data, typically sent to an external location or processed internally. In the browser, the default behavior of submitting form data is not always preferred, as this is done through loading a document, typically the same document, as soon as the form is submitted. In addition, applications have limited control over how the data are formatted on submission with this approach. This is why the new way of sending form data is done through AJAX/fetch requests, wherein the data are serialized into formats like JSON. To turn form data into a specific format requires access to the elements holding the values to each field in the form.
Some libraries for extracting form values query field elements in the DOM, which is inefficient since they need to
traverse the DOM tree in some way, using methods such as document.getElementsByTagName()
and
document.querySelector()
.
Upon retrieving the field values somehow, some libraries attempt to duplicate the values of the fields as they change, for instance by attaching event listeners and storing the new values into some internal object or map, which can be retrieved by some other exposed function.
With formxtra
, there is no need to traverse the DOM for individual fields to get their values. Provided the fields are
associated to the form (either as a descendant of the <form>
element or associated through the form=""
attribute) and has a valid
name
, the values of these fields can be easily extracted, using the form.elements
attribute built-in to the DOM and
used for getting its currently associated fields. With this, only the reference to the form is needed. The current state
of the field elements are already stored in the DOM, waiting to be accessed.
The package can be found on:
For an example form:
<!-- ... -->
<form id="loginForm">
<input type="text" name="username" />
<input type="password" name="password" />
<button type="submit" name="type" value="client">Log In As Client</button>
<button type="submit" name="type" value="admin">Log In As Admin</button>
</form>
<label>
<input type="checkbox" name="remember" form="loginForm" />
Remember my login credentials
</label>
<!-- ... --->
Use the library as follows (code is in TypeScript, but can work with JavaScript as well):
import getFormValues from '@theoryofnekomata/formxtra';
const form: HTMLFormElement = document.getElementById('form');
// optional, but just in case there are multiple submit buttons in the form,
// individual submitters can be considered
const submitter = form.querySelector('[type="submit"][name="type"][value="client"]');
const values = getFormValues(form, { submitter });
const processResult = (result: Record<string, unknown>) => {
throw new Error('Not yet implemented.');
};
// Best use case is with event handlers
form.addEventListener('submit', async e => {
const { target: form, submitter } = e;
e.preventDefault();
const values = getFormValues(form, { submitter });
// Get the form values and send as request to some API
const response = await fetch(
'https://example.com/api/log-in',
{
method: 'POST',
body: JSON.stringify(values),
headers: {
'Content-Type': 'application/json',
},
},
);
if (response.ok) {
const result = await response.json();
processResult(result);
}
})
The library has been tested on the static DOM using JSDOM and Jest, and the real dynamic DOM using Cypress.