Does "generate scaffold -htmx" generate reference fields in the view?

[bobhy]

Using SaaS starter, generating for htmx rendering.
Issuing these commands:

cargo loco generate scaffold --htmx beneficiaries   beneficiary:string!
cargo loco generate scaffold --htmx accounts        account:string! beneficiary:references

I was hoping this would generate an htmx view for accounts that renders the reference field (beneficiary_id) as a dropdown or other select where the options are available values of the foreign key in the referenced table. But I find the generated view doesn't include any beneficiary field:

assets/views/accounts/show.html

{% block content %}
<h1>View accounts: {{ item.id }}</h1>
<div class="mb-10">
    <div>
    <label><b>{{"account" | capitalize }}:</b> {{item.account}}</label>
    </div>
<br />
<a href="/accounts">Back to accounts</a>
</div>
{% endblock content %}

The DB schema looks reasonable:

sqlite> .schema accounts
CREATE TABLE IF NOT EXISTS "accounts" (
    "created_at" timestamp_with_timezone_text NOT NULL DEFAULT CURRENT_TIMESTAMP, 
    "updated_at" timestamp_with_timezone_text NOT NULL DEFAULT CURRENT_TIMESTAMP, 
    "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT, 
    "account" varchar NOT NULL, 
    "beneficiary_id" integer NOT NULL, 
     FOREIGN KEY ("beneficiary_id") REFERENCES "beneficiaries" ("id") ON DELETE CASCADE ON UPDATE CASCADE );

Should I have expected Loco to generate a view with the reference field for me (at 0.14.1)?
If so, can anyone spot what I did wrong? Or offer some suggestions where in the code I can learn how to make this work? I've been all through the existing docs and couldn't find any hints.

If I can get this working, I'll be glad to update the docs for to cover this (common-ish?) scenario. I'd even look into a code change to do this...

I get it that rendering the beneficiary_id field would just show a list of integers, not very interesting. What I really want to show in the dropdown would be a list of beneficiary names, which is the kind of change I'd expect to make myself in the scaffolded view template.

[bobhy]

... a bit more digging into the loco source seems to indicate the scaffold view generator just ignores reference fields altogether (for now).

loco/loco-gen/src/scaffold.rs

Lines 33 to 45 in 96297d6

	let field_type = parse_field_type(ftype)?;
	match field_type {
	crate::infer::FieldType::Reference => {
	// (users, "")
	//references.push((fname.to_string(), String::new()));
	}
	crate::infer::FieldType::ReferenceWithCustomField(_refname) => {
	//references.push((fname.to_string(), refname.clone()));
	}
	crate::infer::FieldType::Type(ftype) => {
	let mappings = get_mappings();
	let rust_type = mappings.rust_field(ftype.as_str())?;
	columns.push((fname.to_string(), rust_type.to_string(), ftype));

I'd be interested in making this work, at least when the field is a reference to one of a few well known lists of FKs that I could cache in the context ahead of time.
Is there any WIP on some other branch that's further along that I could start from?

[kaplanelad]

Hey @bobhy,

At the moment, we don't support references in views.
You're more than welcome to open a PR!