Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Experimental fields #11

Copy link
Copy link
@siilky

Description

@siilky
Issue body actions

Is there an option to properly handle experimental (and not optional) fields (that may or may not be present in implementation as far as I understand that correctly)?
Currently it evaluates directly as json['field'] which throws 'key not found' exception, breaking the whole thing down.

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.