statamic-rad-pack / runway Goto Github PK

When using the provided tag, the ID or any other non-augmented fields for that matter are not available in Antlers for the developer to use.

How to reproduce

Try to reference an {{ id }} while looping with the Runway tag.

What I expected

I expected the non-augmented fields to be available, just not augmented, obviously.

Environment

Statamic 3.0.34 Pro
Laravel 8.18.1
PHP 7.4.3
doublethreedigital/runway dev-master
statamic/ssg 0.2.0

What would you like to see added?

Lots of people recently have been asking for Runway to add support for Live Preview.

What would you like to see added?

It would be really useful, particularly on big blueprints, to target a specific field with an "invalid" UI treatment.

Is there a workaround you can use in the meantime?

Yes you can just look for the field with an asterisk that is not filled in.

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

Description

Pretty much every single state a fieldtype could be in just doesn't seem to work, which is odd. There are listingColumns available.

Loom: https://www.loom.com/share/06afe9eb80d442fea6429c2cacd78fdf

Steps to reproduce

No response

Environment

Latest

Description

When you update values of a record in the control panel, when they are submitted back, we don't seem to do any sort of validation on them.

Description

When I save a Bard field the contents of the field in the edit screen is still json.

Steps to reproduce

config\runway.php

    'resources' => [
        \App\Models\MyModel::class => [
            'name' => 'My Model',

            'hidden' => true,
            // 'icon' => '',

            'blueprint' => [
                'sections' => [
                    'main' => [
                        'fields' => [
                            [
                                'handle' => 'title',
                                'field' => [
                                    'type' => 'text',
                                    'validate' => 'required',
                                ],
                            ],
                            [
                                'handle' => 'body',
                                'field' => [
                                    'type' => 'markdown',
                                    'validate' => '',
                                ],
                            ],
                            [
                                'handle' => 'images',
                                'field' => [
                                    'type' => 'assets',
                                    'container' => 'assets',
                                    'validate' => '',
                                ],
                            ],
                            [
                                'handle' => 'bard_content',
                                'field' => [
                                    'always_show_set_button' => false,
                                    'buttons' => [
                                        'h2',
                                        'h3',
                                        'bold',
                                        'italic',
                                        'unorderedlist',
                                        'orderedlist',
                                        'removeformat',
                                        'quote',
                                        'anchor',
                                        'image',
                                        'table',
                                    ],
                                    'save_html' => false,
                                    'toolbar_mode' => 'fixed',
                                    'link_noopener' => false,
                                    'link_noreferrer' => false,
                                    'target_blank' => false,
                                    'reading_time' => false,
                                    'fullscreen' => true,
                                    'allow_source' => true,
                                    'enable_input_rules' => true,
                                    'enable_paste_rules' => true,
                                    'display' => 'Standard Bard Field',
                                    'type' => 'bard',
                                    'icon' => 'bard',
                                    'listable' => 'hidden',
                                ],
                            ],
                        ],
                    ],
                ],
            ],

            'listing' => [
                'columns' => [
                    'title',
                ],

                'sort' => [
                    'column' => 'title',
                    'direction' => 'asc',
                ],
            ]
        ],
  

database\migrations\2021_06_26_211029_create_my_models_table.php

        Schema::create('my_models', function (Blueprint $table) {
            $table->id();
            $table->string('title');
            $table->string('body')->nullable();
            $table->json('images')->nullable();
            $table->json('bard_content')->nullable();
            $table->timestamps();
        });

app\Models\MyModel.php

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Database\Eloquent\Model;

class MyModel extends Model
{
    use HasFactory;

    // protected $guarded = [];

    protected $casts = [
        'bard_content' => 'json',
    ];
}

Environment

Statamic 3.1.26 Solo
Laravel 8.48.2
PHP 7.4.19
doublethreedigital/runway 2.0.5

What would you like to see added?

I'd like for Runway models to provide their own front-end routes so they act just like collections.

We may be able to achieve this by adding our own repository to this list... https://github.com/statamic/cms/blob/3fab3f0d3b8600da6e597e6a8bb0d63e70502e21/src/Providers/AppServiceProvider.php#L106

^ that list is used for the Data facade which is whats used for content lookups in the FrontendController, so in theory adding a custom repo in there and some other bits and bobs should get us pretty close to a prototype.

If this is something you'd like to see added, please leave a 👍 reaction to this issue.

It would be good to have some use cases listed in the READMe

As per the title:

'sections' => [
    'main' => [
        'fields' => [
            [
                'handle' => 'title',
                'field' => [
                    'type' => 'text',
                    'validate' => 'required',
                ],
            ],
        ],
    ],
],

What would you like to see added?

If you have assigned a route to a resource, it would be great to have a button on the edit entry page to visit the URL, like in standard Statamic.

Is there a workaround you can use in the meantime?

Just remember the route.

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

What would you like to see added?

As title states, when on edit/create model pages it would be great if the native Statamic cmd-s would create and redirect / save.

Is there a workaround you can use in the meantime?

Yes - just click button with the mouse.

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

Description

If you create a new model from e.g. https://statamic-runway-demo.test/cp/runway/mymodel/create

Chrome throws a dirty state warning ( I assume because of the pending redirect ):

Steps to reproduce

1. Load up Chrome
2. Go to create a model
3. Add some data
4. Click save
5. See dirty state warning

Environment

Statamic 3.1.26 Solo
Laravel 8.48.2
PHP 7.4.19
doublethreedigital/runway 2.0.5

It would be nice if Runway provided a fieldtype for each of the models the developer publishes so devs can link to Eloquent records in entries or whatever.

Possibility to export the entries to csv.

What would you like to see added?

My use case:

• OprhanUpdate model
• OrphanUpdate has a since(...carbon...) query scope that returns updates since a given date

I'd love to be able to run that query scope (and potentially more than one query scope) in Antlers like so:

{{ runway:orphanupdate scope="since:some_date" where="...." }}

Should also support multiple query scopes, perhaps like scopes="since:some_date|another_scope"?

Is there a workaround you can use in the meantime?

custom modifiers

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

Description

Hi, it seems that you've commented out in the ListingView.vue component the support for Bulk Actions, while in the documentation you refer to it as doable.

Is there any incombatibility?

Thanks

Steps to reproduce

No response

Environment

Statamic latest version + your latest version on php 8.0

What would you like to see added?

I have Orphans that have many OrphanUpdates via the updates() relationship:

<?php

namespace App\Models;

use App\Models\Country;
use App\Models\OrphanUpdate;
use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Database\Eloquent\Model;

class Orphan extends Model
{
    use HasFactory;

    public function country()
    {
        return $this->belongsTo(Country::class);
    }

    public function updates() {
        return $this->hasMany(OrphanUpdate::class);
    }
}

Would be great if I could do this:

{{ runway:orphan where="id:{orphan}" }}
DETAIL PAGE
<img src="{{ image }}">
<h2>{{ name }}</h2>
<p>{{ summary }}</p>

<h3>Updates</h3>
<ul>
    {{ updates }}
        <li>
            {{ text }}
        </li>
    {{ /updates }}
</ul>
{{ /runway:orphan }}

Is there a workaround you can use in the meantime?

query the orphanupdate resource directly.

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

I know what I mean.

Description

To change models. to resources. when upgrading to v2.0 of Runway.

Show specific BelongsTo field in Listing for example:

        \App\Models\Booking::class => [
            'name' => 'Bookings',
            'blueprint' => [
                'sections' => [
                    'main' => [
                        'fields' => [
                            /*
                            [
                                'handle' => 'title',
                                'field' => [
                                    'type' => 'text',
                                    'validate' => 'required',
                                ],
                            ],
                            */],
                    ],
                    'sidebar' => [
                        'fields' => [
                            [
                                'handle' => 'property_id',
                                'field' => [
                                    'type' => 'belongs_to',
                                    'resource' => 'property',
                                    'max_items' => 1,
                                    'mode' => 'select',
                                    'validate' => 'required',
                                ],
                            ]
                        ]
                    ]
                ],
            ],
            'listing' => [
                'columns' => [
                    'id',
                    'property_id'
                ],

                'sort' => [
                    'column' => 'id',
                    'direction' => 'asc',
                ],

                'cp_icon' => '<svg xmlns="http://www.w3.org/2000/svg" width="19" height="19" fill="currentColor" class="bi bi-calendar-range" viewBox="0 0 16 16">
                                <path d="M9 7a1 1 0 0 1 1-1h5v2h-5a1 1 0 0 1-1-1zM1 9h4a1 1 0 0 1 0 2H1V9z"/>
                                <path d="M3.5 0a.5.5 0 0 1 .5.5V1h8V.5a.5.5 0 0 1 1 0V1h1a2 2 0 0 1 2 2v11a2 2 0 0 1-2 2H2a2 2 0 0 1-2-2V3a2 2 0 0 1 2-2h1V.5a.5.5 0 0 1 .5-.5zM1 4v10a1 1 0 0 0 1 1h12a1 1 0 0 0 1-1V4H1z"/>
                            </svg>',

            ],
        ],

What would you like to see added?

Once #46 is merged, I think it would be a good time to get rid of our custom listing buttons system and use Actions instead.

Is there a workaround you can use in the meantime?

Just continue to use listing buttons 🤷‍♂️

Priority wise - where's this feature for you?

I'm going to need it at some point in the future but it's not major right now.

Description

I have an existing model that uses the Spatie/Sluggable package, and uses the getRouteKeyName() method to set a custom route key: 'slug'. The listing page of Runway uses the 'id' field to generate the edit link (eg. http://localhost/cp/runway/product/1), but the Resource Controller edit method uses the routeKey() method in retrieving the model record. So it is trying to find a record whose slug is '1'. This results in an "Attempt to read property "name" on null" error, since the record cannot be retrieved.

Steps to reproduce

1. Add getRouteKeyName() method to your model returning a key name other than 'id' (eg. 'slug')
2. Navigate to a Runway index page and try to edit a record

Environment

Statamic 3.1.27 Solo
Laravel 8.42.1
PHP 8.0.7
doublethreedigital/runway 2.1.1

There's a couple of improvements I'd like to make to the index listing:

• Ability for filters, just like the entries listing
• Real-time search (over AJAX, instead of full page reloads)
• Confirmation on the delete action #13
• Ability to use Actions on the Runway listing #14

I still need to investigate how this would work behind the scenes, especially with the filters..

How should it work?

Will probably need to convert the index listing from Blade to Vue so I can do the real-time-ness that's required for some of the features.

Use cases

Where you want to use Runway as a replacement for entries.

This could be nice if you had a table of orders and you don't want any users to delete any orders due to them needing to be kept for legal purposes.

Description

Whenever you use the slug fieldtype in a blueprint, it will cause an error which gets rid of the text field altogether. I believe it's something to do with stuff in the Vuex store.

Exact steps to reproduce

1. Add slug fieldtype to Runway blueprint

Environment

Runway, after #30

What would you like to see added?

This is something I've told a couple of people about but essentially, my plan at some point is to build a way to automatically generate database migrations, based on field configurations from your blueprint.

How would it work?

It would be smart enough to know which column type each builtin fieldtype should be and it would be clever to change that if max_assets is defined.

If we don't know which column type to use (eg. custom fieldtype) we could maybe just leave it as a string/json column and give the user an error?

This would be some sort of command, like: php please runway:migration order

Considerations

• It would also need to know how to handle changes in a blueprint (eg. field added, field removed, field config changed, etc). I guess in that case we'd just need to do a comparison to what's there and make a new migration with the relevant changes.

Is there a workaround you can use in the meantime?

You could just do it by hand, which is a bit of a sucky option because you then have to define everything twice.

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

Description

For some reason, when you're using the Asset fieldtype on a resource and you attempt to use it as if it's augmented in a front-end template, it doesn't show:

{{ images }}
  {{ url }}
{{ /images }}

Exact steps to reproduce

1. Add asset field to runway blueprint
2. Actually add an asset to a model
3. Try to use the 'augmented' value of the asset field in your template.

Environment

Runway, after #28

Description

The data is rendered just "as-is". For example a date field gets rendered like this in collections:

But in runway it's like this:

Steps to reproduce

No response

Environment

Statamic 3.1.26 Pro
Laravel 8.49.0
PHP 8.0.6
doublethreedigital/runway 2.1.0

What would you like to see added?

Use case:

• I have Orphan which hasMany OrphanUpdates via a updates relationship
• have additional sponsorUpdates relationship on Orphan

Would like to be able to use that relationship in the {{ runway:orphan ... }} like so:

{{ runway:orphan with="sponsor_updates" ... }}

{{ sponsor_updates }}
...
{{ /sponsor_updates }}

Is there a workaround you can use in the meantime?

Likely a custom modifier or tag

Priority wise - where's this feature for you?

This is sort of a blocker for me/this project.

What would you like to see added?

Have the eloquent models that are used inside runway accessible by the search index.
This on its turn would make them available in the site wide search, if algolia is configure they'd move into there as well I think?
And using the search index on the frontend would also make them accessible there.

Adding the models to searchables would open them up to a lot of places!

Is there a workaround you can use in the meantime?

Not really no

Would you be open to PR'ing the feature?

I could share some classes from the Statamic core I looked into when I tried extending it myself.
But I think you'd get there quite easily. Like discussed on discord did would probably need changes in the statamic core.

What would you like to see added?

For headless sites with lots of entries, this could be the killer feature thats currently missing in Statamic. Being able to store some Collections in a database would be the perfect solution.

Would be great to be able to enable GraphQL for certain models. Sometimes we just add models that just hold data and shouldn't be publicly queryable.

Is there a workaround you can use in the meantime?

Not that I can think of, is the data available in the content api?

Priority wise - where's this feature for you?

I'm going to need it at some point in the future but it's not major right now.

What would you like to see added?

Might be nice if we could create an integration with Blaze so we can kinda cross-promote that addon.

Is there a workaround you can use in the meantime?

Build my own, rely on the CP Nav Item search thingy?

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

I'm trying to deploy a project with Runway to a new Forge server but I'm running into issue when I run composer install, either from inside Forge or via SSH. Here's the output:

> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

   Illuminate\Database\QueryException

  SQLSTATE[HY000] [1045] Access denied for user 'homestead'@'localhost' (using password: YES) (SQL: select column_name as `column_name` from information_schema.columns where table_schema = homestead and table_name = payments)

  at vendor/laravel/framework/src/Illuminate/Database/Connection.php:678
    674▕         // If an exception occurs when attempting to run a query, we'll format the error
    675▕         // message to include the bindings with SQL, which will make this exception a
    676▕         // lot more helpful to the developer instead of just the database's errors.
    677▕         catch (Exception $e) {
  ➜ 678▕             throw new QueryException(
    679▕                 $query, $this->prepareBindings($bindings), $e
    680▕             );
    681▕         }
    682▕

  1   [internal]:0
      DoubleThreeDigital\Runway\Support\ModelFinder::DoubleThreeDigital\Runway\Support\{closure}()

      +2 vendor frames
  4   [internal]:0
      DoubleThreeDigital\Runway\Support\ModelFinder::DoubleThreeDigital\Runway\Support\{closure}()
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

How to reproduce

Install the pman project on forge (I know the one)

What I expected

For the install process to work absolutely fine.

Environment

Can't run command so unsure.

What would you like to see added?

HasMany, HasOne etc.

Is there a workaround you can use in the meantime?

Not sure.

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

Runway should respect the getRouteKey method on Eloquent models which defines the model key used in URLs. This is helpful in large applications where you don't want to expose incrementing IDs to the end user.

How to reproduce

Add this method to an Eloquent model and try to visit a Runway edit publish form. It uses the record ID. (Note to self: see on pod project)

public function getRouteKey()
{
    return 'uuid';
}

What I expected

I expected that the URL would use the UUID value, instead of the incrementing id.

Environment

Statamic 3.0.34 Pro
Laravel 8.18.1
PHP 7.4.3
aryehraber/statamic-captcha 1.1.0
doublethreedigital/runway 1.0.1

Description

I have a date field (sql type date) with this in the blueprint:

        handle: birthdate
        field:
          mode: single
          time_enabled: false
          time_required: false
          earliest_date: '1900-01-01'
          full_width: false
          inline: false
          columns: 1
          rows: 1
          display: Birthdate
          type: date
          icon: date

When I try to load a model detail page in the CP I get a carbon error:

Steps to reproduce

1. have a date field in the blueprint
2. try to load a model in the CP

Environment

Statamic 3.2.16 Pro
Laravel 8.64.0
PHP 8.0.11
aryehraber/statamic-captcha 1.5.2
aryehraber/statamic-uuid 2.0.3
doublethreedigital/runway 2.1.27
edalzell/download dev-main
edalzell/forma 1.0
jonassiewertsen/statamic-livewire 2.7.0
statamic/seo-pro 2.3.2
transformstudios/events 2.2.2
transformstudios/front 1.7.1
transformstudios/gated dev-main
transformstudios/magic-link dev-main
transformstudios/memorial dev-feature/orphan-portal
transformstudios/price-of dev-feature/orphan-portal
transformstudios/review 3.1
transformstudios/simple dev-main
transformstudios/stripe dev-main
transformstudios/takeover-redirects dev-main

What would you like to see added?

It would be nice for this addon to bring support for the Statamic Content API.

If we implement #54, it makes sense we introduce this as well.

Is there a workaround you can use in the meantime?

You could build your own API endpoints with Resources and just get the data out that way.

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

Description

We've got an app where we're using Runway for the front-end marketing site and we're using Inertia.js in the backend for the web app.

It seems like whenever the Responsable interface is on a model, it causes Inertia.js to break, causing the below error:

Steps to reproduce

1. Setup Runway front-end for a model
2. Use Inertia.js with route model binding for the same model
3. See issue with Inertia route

Environment

Statamic 3.1.32 Pro
Laravel 8.54.0
PHP 7.4.13
doublethreedigital/duplicator 1.3.3
doublethreedigital/runway 2.1.5
doublethreedigital/simple-commerce 2.3.18

I think it could be a good idea to show a search form on the listing table for search.

Runway provides a delete action on records but it would be nice if there was a confirmation modal that comes up as part of that so a user doesn't accidentally delete the wrong record.

What would you like to see added?

The new HasMany Fieldtype is great, thanks for this.

For our use case we'd like one of 2 things:

1. it to act like the Entries type, where you can click on the item and have the stack slide out.
2. be able to click on the item and get taken to its edit page, as well as being able to choose columns to see.

Is there a workaround you can use in the meantime?

Nope, for our use case we can't use this field.

Priority wise - where's this feature for you?

This is sort of a blocker for me/this project.

Description

When I install Runway I'm somehow unable to delete any entries, taxonomies, or assets. The delete buttons are removed from tables and action dropdown. I can still delete blueprints and fieldsets.

Steps to reproduce

CP without Runway installed:

CP with Runway installed:

If I uninstall Runway the delete buttons come back. I have tried different combinations of Runway and Statamic versions, but they all give the same result.

Environment

Statamic 3.2.4 Solo
Laravel 8.61.0
PHP 7.4.12
doublethreedigital/runway 2.1.21

Description

When I try to edit a model in my resource, the screen goes white after a few seconds. Presumably to do with something we're doing with custom publish forms.

Exact steps to reproduce

1. Go to a resource
2. Click on record to view it
3. Screen goes white

Environment

Statamic 3.1.16 Pro
Laravel 8.43.0
PHP 8.0.3
aryehraber/statamic-captcha 1.5.1
doublethreedigital/duplicator 1.3.2
doublethreedigital/runway 2.0.2
octoper/statamic-html-minify 0.0.5

Description

I have a resource OrphanUpdate. When used in a template I need to do {{ runway:orphanupdate ... }} instead of {{ runway:orphan_update ... }} like I'd expect.

Steps to reproduce

1. Have a CamelCased resource FooBar
2. Attempt to reference in a template like {{ runway:foo_bar ... }}

Environment

Statamic 3.1.32 Pro
Laravel 8.53.1
PHP 8.0.9
aryehraber/statamic-captcha 1.5.2
aryehraber/statamic-uuid 2.0.3
doublethreedigital/runway 2.1.5
edalzell/forma 0.8.12
jonassiewertsen/statamic-livewire 2.6
statamic/seo-pro 2.2.1
transformstudios/events 2.2
transformstudios/front 1.2.1
transformstudios/magic-link dev-main
transformstudios/memorial dev-feature/orphan-portal
transformstudios/price-of dev-feature/orphan-portal
transformstudios/review 3.1
transformstudios/simple dev-main
transformstudios/stripe dev-main
transformstudios/takeover-redirects dev-main

Add the instructions to the changelog of v2.0.0 so users know what they need to do. Similarly to what we did for Simple Commerce.

https://github.com/doublethreedigital/runway/releases/tag/v2.0.0

Description

For Bard etc, you'll need the column to be JSON and cast to JSON in your Eloquent model. I should probably add documentation around this.

What would you like to see added?

It would be good to have a php please runway:blueprint Order. Where the schema of the model could be mapped, or best guessed, to a fieldtype and generate a blueprint based on that.

So that when statamic/cms#3963 is hopefully merged, you can go and make the amendments to the blueprint but the skeleton would be there to modify.

Is there a workaround you can use in the meantime?

Yep. Manually look up the column type -> fieldtype pairing and write the blueprint array.

Priority wise - where's this feature for you?

This is just a nice to have. I can deal without.

What would you like to see added?

Be able to use Statamic GUI to view and edit runway blueprints from the CP. I assume that is what this idea is about: statamic/ideas#408

Is there a workaround you can use in the meantime?

Yep - just do it manually.

Would you be open to PR'ing the feature?

Yes.

What would you like to see added?

Currently using Runway to build out an orphan sponsorship feature. The customer signs up for a sponsorship, indicating their preferences (gender, country, etc). First pass will be a manual process to find the most appropriate orphan, and do that we need to be able to filter on fields (like gender, country) to find the best one.

Is there a workaround you can use in the meantime?

Not really, can only do a single column sort

Priority wise - where's this feature for you?

This is sort of a blocker for me/this project.

It might be a good idea to provide some screenshots on the Marketplace listing of Runway.