Skip to content

README - Inconsistent reference to cfg.body / cfg.form #40

Description

@mdmdj

It seems that in 1 location the README references evt.detail.cfg.form where it should reference evt.detail.cfg.body .

README as of https://github.com/bigskysoftware/fixi/blob/d31fc1d4128ecf957f48b7d0bbea879eaa53f81d/README.md

https://github.com/bigskysoftware/fixi#requests states:

You can add or remove values using the evt.detail.cfg.form FormData object in the fx:config event.

https://github.com/bigskysoftware/fixi#fxconfig states:

This config object has the following properties:
[...]
body - The body of the request, if present, a FormData object that holds the data of the form associated with the request

(there seems to be no other mention of cfg.form)

fixi.js as of https://github.com/bigskysoftware/fixi/blob/d31fc1d4128ecf957f48b7d0bbea879eaa53f81d/fixi.js
Line 23 defines cfg.body
Line 36 and 39 refer to cfg.body

There is no definition or reference to cfg.form that I could find.

Therefore it seems that the reference to evt.detail.cfg.form is incorrect and should reference evt.detail.cfg.body .

LLM Disclosure: While asking an LLM to suggest methods of doing a specific task using fixi and providing the README and source code as reference, the output mentioned this as a side note. I've done my best to verify all the details manually as explained above and this report was written entirely manually.
Why ask an LLM when fixi is so simple? Web and JavaScript is not the focus of my study at this time, I need UI for my backend and I sometimes need to get unstuck. If I'm wrong please forgive the inconvenience. I'm a big fan 🙏

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions