Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change types entry #53

Closed
Pikachu920 opened this issue May 7, 2018 · 1 comment
Closed

Change types entry #53

Pikachu920 opened this issue May 7, 2018 · 1 comment
Assignees
Labels
priority: medium Requires some attention, but does not need to be deployed immediately (most bugs) type: enhancement

Comments

@Pikachu920
Copy link

Is your feature request related to a problem? Please describe.
I'm always frustrated when I am unable to enforce change types at parse time when possible.

Describe the solution you'd like

expression something:
  change types: number, location
  get:
    # ...
  set:
    # ...

Describe alternatives you've considered
Checking the change value's type at runtime, but this doesn't allow for parse time errors.

@btk5h
Copy link
Owner

btk5h commented May 7, 2018

I'm planning on allowing acceptable change types to be set per change mode.

expression something:
  set number, location:
    # ...

@btk5h btk5h added the priority: medium Requires some attention, but does not need to be deployed immediately (most bugs) label Aug 13, 2018
@btk5h btk5h self-assigned this Aug 21, 2018
@btk5h btk5h closed this as completed in ab853fa Aug 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium Requires some attention, but does not need to be deployed immediately (most bugs) type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants