Closes #7

Calling FrontController throws a 404 if the data doesn't exist. Calling the actual lookup is better.

@hotmeteor sorry I didn't write a test, but the tests don't run (blueprint is missing). I can help get those going again, if you like.

Please update inertiajs/inertia-laravel support:

$ composer require hotmeteor/inertia-statamic
Using version ^0.1.2 for hotmeteor/inertia-statamic
./composer.json has been updated
Running composer update hotmeteor/inertia-statamic
> Statamic\Console\Composer\Scripts::preUpdateCmd
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires hotmeteor/inertia-statamic ^0.1.2 -> satisfiable by hotmeteor/inertia-statamic[v0.1.2].
    - hotmeteor/inertia-statamic v0.1.2 requires inertiajs/inertia-laravel ^0.4.1 -> found inertiajs/inertia-laravel[v0.4.1, ..., v0.4.5] but it conflicts with your root composer.json require (^0.6.3).

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require hotmeteor/inertia-statamic:*" to figure out if any version is installable, or "composer require hotmeteor/inertia-statamic:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Got the Statamic error sorted.

However @hotmeteor, I had to change the expected view results as there's an extra <p> in what's returned and I don't know why.

Also, the last test still fails cuz there's an extra newline in the results, which doesn't make sense to me.

If you have custom, non-statamic routes, a 404 is thrown from the adapter.

We found this when enabling OAuth for Statamic. Statamic then adds the /oauth/{provider} route, that throws a 404.

PR incoming.

Disclaimer - I did this all in the GitHub editor. I didn't actually test it, so you'll probably want to check it out.

While I was doing https://github.com/statamic/cms/pull/5302 for Statamic 3.3, I went looking on GitHub for usages of augmentValue() and noticed this.

1. On Statamic 3.2, if you had a field in your blueprint named template, $this->augmentedValue('template') would have been a Value instance, so this condition would always be false.
2. On Statamic 3.3, even if you don't have a field named template, $this->augmentedValue('template') will be a Value instance, again making this condition always false.
3. You can just use the template() method to get the plain template name.
4. I swapped the instanceof check to first, so you can be sure the template() method will be available to use since you'll know it's a Page or Entry already.

This seems to work pretty ok, but it does not load related data.

So if I use the Entries field, then the entry is not resolved. That means I have to fetch it via the api_url, but this really fucks with SSR, since this is not loaded then.

Is there a way to load all data in, not just what is on the given page?

Hi guys,

Does anyone know how can I get metadata of images stored on S3?

The props returned on the page gives me data like url, id, permalink, etc.. but no alt tag, width, height, etc...

I had the same problem with forms and their fields and I solved it by making an AJAX call to the controller and pulling all the data I need by passing form handle and returning the data aj JSON.

Do I need to do something similar with an image? Blade and antlers can somehow pull it out just by doing $image->alt or $image->height but that's not an option with Vue as the prop is just not there.

Any ideas are welcome.

Thank you

Problem description:

const app = createApp({
    render: () =>
        h(App, {
            initialPage: JSON.parse(el.dataset.page),
            resolveComponent: name => pages[`./Pages/${name}.vue`].default
        }),
});

Error:

Cannot read properties of undefined (reading 'default')

I did some digging and found that the issue comes from InertiaStatamic.php

public function handle(Request $request, Closure $next)
    {
        $page = app(FrontendController::class)->index($request);
      
        if ($page->augmentedValue('template') === 'app' && ($page instanceof Page || $page instanceof Entry)) {
            return Inertia::render(
                $this->buildComponentPath($page),
                $this->buildProps($page)
            );
        }

        return $next($request);
    }

$page->augmentedValue('template') === 'app' => Always returns false

Possible fix

Got it working by adding raw()

$page->augmentedValue('template')->raw() === 'app' => Returns true if app template exists.

Thanks!

Hey,

I've tried making this work with Vue 2 using the following code as per the Inertia documentation:

import Vue from 'vue'
import { createInertiaApp } from '@inertiajs/inertia-vue'

createInertiaApp({
  resolve: name => require(`./Pages/${name}`),
  setup({ el, App, props }) {
    new Vue({
      render: h => h(App, props),
    }).$mount(el)
  },
})

But I'm seeing the following console error:

Uncaught (in promise) Error: Cannot find module './undefined'

I'm assuming this could be an issue where the statamic/inertia adapter isn't communicating the path for the components?

Thanks!

I'm trying to implement this connector (v0.1.2) in my Statamic v3.1.23 site and I'm getting this undefined variable $page error.

When troubleshooting, I've discovered it's happening due to $page->augmentedValue('template') === 'app' being false (in InertiaStatamic.php), so the Inertia render isn't triggered. If I note out this conditional statement, then the page seems to load!

From what I can tell now, there's no template value being augmented anymore that indicates which template is rendering the requested path?

This is definitely confusing...

Help?

Thanks so much!