Hi,

Great work on this, thanks for building it.

I noticed that Applications are not nodes. This seems to be creating additional work for your development.

For example, another user posts here that all employers can see each other's applications.

If this Applications were nodes, the admin could use a content permissions module to restrict the viewing of Applications to the owner and/or associated user, or in other words the Applicant and the Employer.

It may make rules integrations easier as well.

If you have a good reason not to make them nodes, then I understand.

Thanks

Shawn

Comments

kaizerking’s picture

kaizerking CreditAttribution: kaizerking commented

there are two types of applications perhaps that is the reason they are made as separate entities

alexweber’s picture

alexweber CreditAttribution: alexweber commented
Assigned: Unassigned » alexweber
Status: Active » Fixed

Hi and thanks for bringing this up!

Despite being much simpler to deal with, nodes have a bit of overhead and are primarily meant for content, strictly speaking.

Also, as kaizerking mentioned, if we used nodes we wouldn't be able to have different fieldable application types.

Sure, its a bit more work, but most of the heavy lifting is done by Entity API anyway! :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.